Data lifecycle discovery and management

ABSTRACT

Techniques for data lifecycle discovery and management are presented. Data lifecycle discovery platform (DLDP) can identify data of users, data type, and language of data stored in data stores (DSs) of entities based on scanning of data from databases. DLDP determines compliance of DLDP and DSs with obligations relating to data protection arising out of jurisdictional laws or agreements. DLDP generates rules to facilitate complying with and enforcing laws and agreements. DLDP can determine, and present to authorized users, risk scores relating to levels of compliance of the DLDP, associated platforms, or entities, risk indicator metrics, or a privacy health index of the organization associated with DLDP. DLDP can manage user rights regarding data, and access to data in DSs and information relating thereto stored in secure data store of DLDP. DLDP can remediate issues involving anomalies indicating non-compliance. DLDP can utilize machine learning to enhance various functions of DLDP.

TECHNICAL FIELD

The subject disclosure relates generally to electronic information andcommunications, and more specifically to data lifecycle discovery andmanagement.

BACKGROUND

Data can be electronically communicated (e.g., via communicationnetworks), exchanged, stored, and displayed in connection with varioustypes of communications, transactions (e.g., purchases, subscriptions,exchanges, etc.), or other interactions. For example, users can utilizevarious online and digital services to manage financial accounts, makepayments on bills from financial accounts, purchase goods and servicesfrom businesses via websites of businesses, or send or transfer money toanother person. For instance, there are digital wallet services thatenable a person to use a communication device (e.g., mobile phone orcomputer) and an application (e.g., mobile digital wallet application)to transfer money, via an electronic transfer, from the person's digitalwallet to another digital wallet of another entity, such as a friend orbusiness. Users also can make online purchases for products or serviceswhere such purchases can be paid via electronic payment from bankaccounts or credit accounts of the users.

In connection with the various types of online interactions, the data ofusers, businesses, and other entities can be communicated to variousparts of the world and/or stored in various databases in various partsof the world. The data can include sensitive and/or personal data ofentities (e.g., financial account numbers, financial information, SocialSecurity Numbers, personal identification information, authenticationinformation, and/or transaction information of entities). It is can bedesirable to maintain the security of the data of users, businesses, andother entities, to ensure that only authorized entities are able toaccess and use the data, particularly sensitive and/or personal data, sothat unauthorized and/or malicious users are not able to gain access tothe data and/or so such data is not otherwise undesirably exposed andused. Further, laws and agreements have been implemented that cancondition the access and use of data, particularly sensitive and/orpersonal data, in an effort to protect such data.

Conventional techniques, applications, and online and digital servicesrelating to the communication, exchange, storage, access, and display ofdata can be deficient in protecting data of users, businesses, and otherentities, and can be inefficient in implementation, can be undesirablylimited in scope, and can be lacking in robustness, which can negativelyimpact the protection of such data.

Systems, methods, and/or techniques that can ameliorate one or more ofthese and other deficiencies of conventional technology can bedesirable.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an example, non-limiting systemthat can employ a data lifecycle discovery platform (DLDP) that candesirably discover and track data stored in various data stores andmanage the data, in accordance with various aspects and embodiments ofthe disclosed subject matter.

FIG. 2 depicts a block diagram of an example system that can utilizeclassification techniques, and artificial intelligence and machinelearning techniques, to facilitate classifying or identifying datascanned from data stores to facilitate desirably discovering andtracking data stored in various data stores and managing the data, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 3 depicts a block diagram of an example system that can illustratea DLDP process flow in connection with the DLDP desirably discoveringand tracking data stored in various data stores and managing the data,in accordance with various aspects and embodiments of the disclosedsubject matter.

FIG. 4 illustrates a block diagram of an example system that can manageuser data rights, governance, and data discovery with regard to data ofusers and information relating to the data of users that is stored inthe DLDP or in data stores associated with the DLDP to facilitatedesirably protecting and securing data of users and information relatingthereto, in accordance with various aspects and embodiments of thedisclosed subject matter.

FIG. 5 presents a diagram of an example user interface relating toexample data that can be presented to a user by the DLDP 102 in responseto a data request, in accordance with various aspects and embodiments ofthe disclosed subject matter.

FIG. 6 presents a diagram of an example user interface relating toexample data that can be presented in a first language to a user by theDLDP in response to a data request, in accordance with various aspectsand embodiments of the disclosed subject matter.

FIG. 7 presents a diagram of an example user interface relating toexample data that can be presented in a second language to a user by theDLDP in response to a data request, in accordance with various aspectsand embodiments of the disclosed subject matter.

FIG. 8 depicts a diagram of an example user interface that can compriseinformation relating to data collection with regard to data associatedwith an entity, in accordance with various aspects and embodiments ofthe disclosed subject matter.

FIG. 9 illustrates a diagram of an example user interface that cancomprise information relating to access of data and access controls tocontrol access to data associated with an entity, in accordance withvarious aspects and embodiments of the disclosed subject matter.

FIG. 10 depicts a diagram of an example user interface that can compriseinformation relating to data sharing of data associated with an entitywith third party entities, in accordance with various aspects andembodiments of the disclosed subject matter.

FIG. 11 illustrates a block diagram of an example system that can employa governance component to facilitate governing the DLDP and associatedsystems, data stores, data, etc., of entities, data sharing, andcompliance with laws, regulations, and agreements, in accordance withvarious aspects and embodiments of the disclosed subject matter.

FIG. 12 presents a diagram of an example risk score matrix system thatcan be used to facilitate determining risk scores associated with anentity, in accordance with various aspects and embodiments of thedisclosed subject matter.

FIG. 13 presents a diagram of example sources that can be accessed toobtain data that can be used to determine key risk indicators (KRIs), inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 14 depicts a block diagram of an example risk score and privacyhealth index process flow that can be used to facilitate determiningrisk scores and a privacy health index associated with an entity, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 15 presents a diagram of an example exception message relating toan example anomaly issue relating to data subject requests, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 16 illustrates a diagram of an example governance flow forgoverning the collecting, processing, accessing, storing, sharing, andutilization of data of users and information relating to data of users,in accordance with various aspects and embodiments of the disclosedsubject matter.

FIG. 17 illustrates a diagram of an example user interface of a privacyhub that can provide information regarding KRI metrics associated withprivacy principles, risk scores, a privacy health index, and otherinformation, in accordance with various aspects and embodiments of thedisclosed subject matter.

FIG. 18 depicts a diagram of an example user interface that can providevarious information regarding data subject requests of users, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 19 presents a diagram of example graphs that can provideinformation regarding certain opt in and opt out trends, in accordancewith various aspects and embodiments of the disclosed subject matter.

FIG. 20 presents a diagram of an example graph that can provideinformation regarding marketing opt-out exception incidents in relationto total email messages sent by an entity during a given time period, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 21 presents a diagram of an example graph that can provideinformation regarding cookie consents of users associated with an entityin relation to consents associated with unregistered countries during agiven time period, in accordance with various aspects and embodiments ofthe disclosed subject matter.

FIG. 22 presents a diagram of an example graph that can provideinformation regarding a personalization trend within an entity and thirdparty entities during a given time period, in accordance with variousaspects and embodiments of the disclosed subject matter.

FIG. 23 depicts a block diagram of an example system that can beemployed by the DLDP and its constituent or associated platforms tofacilitate managing data of users, in accordance with various aspectsand embodiments of the disclosed subject matter.

FIG. 24 depicts a block diagram of an example system that can comprise aDLDP that can utilize containerized application technology, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 25 illustrates a block diagram of an example open source stack thatcan be employed by the DLDP and its constituent or associated platforms,in accordance with various aspects and embodiments of the disclosedsubject matter.

FIG. 26 illustrates a block diagram of an example system that can employan application programming interface (API) and server to facilitateenabling client applications and devices to query and access data, tofacilitate desirable processing and communication of data of users inconnection with the DLDP, in accordance with various aspects andembodiments of the disclosed subject matter.

FIG. 27 depicts a block diagram of an example system that can supportmultiple tenant entities to facilitate desirably managing data of usersand information relating thereto with regard to multiple tenant entitiesassociated with the DLDP, in accordance with various aspects andembodiments of the disclosed subject matter.

FIG. 28 depicts a flow diagram of an example, non-limiting method thatcan desirably manage data discovery of data stored in data storesassociated with one or more entities to facilitate determiningcompliance of the data stores and entities with obligations arising outlaws and/or agreements relating to data protection, in accordance withvarious aspects and embodiments described herein.

FIG. 29 illustrates a flow diagram of an example, non-limiting methodthat can desirably determine a set of rights of a user with regard todata of the user that is stored in a set of data stores associated withan entity, in accordance with various aspects and embodiments describedherein.

FIG. 30 illustrates a flow diagram of an example, non-limiting methodthat can desirably determine a set of obligations and corresponding setof rules relating to data protection, and determine compliance with theset of obligations by a set of data stores and associated entity, inaccordance with various aspects and embodiments described herein.

FIG. 31 illustrates a flow diagram of another example, non-limitingmethod that can desirably identify data, data types of data, andlanguages of data stored in data stores associated with entities, inaccordance with various aspects and embodiments described herein.

FIG. 32 illustrates a flow diagram of another example, non-limitingmethod that can desirably determine respective risk scores associatedwith KRI metrics, privacy principles, and/or data management platforms,in accordance with various aspects and embodiments described herein.

FIG. 33 illustrates a flow diagram of another example, non-limitingmethod that can desirably determine a privacy health index associatedwith an entity that is associated with a set of data stores that storedata of users, in accordance with various aspects and embodimentsdescribed herein.

FIG. 34 presents a flow diagram of an example, non-limiting method thatcan determine and utilize a set of rules that can correspond to the setof obligations application to a set of data stores, an associatedentity, and/or the DLDP and its constituent or associated platforms, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 35 depicts a flow diagram of an example, non-limiting method thatcan determine an anomaly with regard to data of users has been detectedand initiate a remediation action to remedy or mitigate the anomaly, inaccordance with various aspects and embodiments of the disclosed subjectmatter.

FIG. 36 illustrates a block diagram of an example, non-limitingoperating environment in which one or more embodiments described hereincan be facilitated.

FIG. 37 illustrates an example networking environment operable toexecute various implementations described herein.

DETAILED DESCRIPTION

The following detailed description is merely illustrative and is notintended to limit embodiments and/or application or uses of embodiments.Furthermore, there is no intention to be bound by any expressed orimplied information presented in the preceding Background or Summarysections, or in the Detailed Description section.

One or more embodiments are now described with reference to thedrawings, wherein like referenced numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea more thorough understanding of the one or more embodiments. It isevident, however, in various cases, that the one or more embodiments canbe practiced without these specific details.

Data can be electronically communicated (e.g., via communicationnetworks), exchanged, stored, and displayed in connection with varioustypes of communications, transactions (e.g., purchases, subscriptions,exchanges, etc.), or other interactions. In connection with the varioustypes of online interactions, the data of users, businesses, and otherentities can be communicated to various parts of the world and/or storedin various data stores in various parts of the world. The data caninclude sensitive data, private data, personal data, protected data,and/or personally identifiable information (PII) of users or otherentities (e.g., financial account numbers, financial information, SocialSecurity Numbers, personal identification information, authenticationinformation, and/or transaction information of users or other entities),and/or information relating to such data. It is can be desirable tomaintain the security of the data of users, businesses, and otherentities, and information relating to such data, to ensure that onlyauthorized entities are able to access and use the data, particularlysensitive data, private data, personal data, protected data, and/or PII,so that unauthorized and/or malicious users are not able to gain accessto the data and/or so such data is not otherwise undesirably exposed andused. Further, governmental agencies of various jurisdictions haveimplemented various laws and regulations that can condition the accessand use of data, particularly sensitive data, private data, personaldata, protected data, and/or PII, and/or can otherwise specifyparticular data protections, in an effort to protect such data. Also,there often can be agreements (e.g., contracts) between entities thatcan specify how data is to be handled, can condition the access and useof data, particularly sensitive data, private data, personal data,protected data, and/or PII, and/or can otherwise provide for theprotection of data.

Conventional techniques, applications, and online and digital servicesrelating to the communication, exchange, storage, access, and display ofdata can be deficient in protecting data of users, businesses, and otherentities, can be inefficient in implementation, can be undesirablylimited in scope, can be lacking in robustness, and can fail to providesufficient information regarding the handling and usage of data byentities, each and all of which can negatively impact the protection ofsuch data.

Various embodiments of the disclosed subject matter can address one ormore of these issues/problems by facilitating desirable (e.g.,efficient, enhanced, robust, and/or optimal) data lifecycle discoveryand management. One or more embodiments described herein includesystems, computer-implemented methods, apparatus, and/or computerprogram products that can facilitate data lifecycle discovery andmanagement.

To that end, techniques for data lifecycle discovery and management arepresented. A data lifecycle discovery platform (DLDP) can identify dataof users, data type, and language of the data stored in data stores(e.g., database components or other data stores) of entities based atleast in part on scanning of the data stored in the data stores (e.g.,by a scanner component of or associated with the DLDP). The DLDP can bea multi-tenant, multi-lingual platform that can support multiple tenantsand multiple languages. The DLDP or an associated platform (e.g.,governance platform) can determine compliance (e.g., a level ofcompliance) of the DLDP and the data stores with obligations (e.g.,legal and/or contractual requirements, responsibilities, duties,constraints, or provisions) relating to data protection (e.g., dataprotection, privacy, and security) that can arise out of applicable lawsor regulations of jurisdictions (e.g., associated with the entity, datastore, or DLDP) or agreements (e.g., service-level agreements (SLAs))between entities. Based at least in part on the results of analyzing theapplicable laws, regulations, and/or agreements, the DLDP or theassociated platform can employ a rules engine to determine and generaterules to facilitate complying with and enforcing laws, regulations,and/or agreements.

The DLDP can comprise or be associated with a rights management platformthat can manage rights of users with regard to their data andinformation relating to their data, and can manage access to data storedin the data stores and the information relating thereto, wherein thedata or the information relating thereto can be stored in a secure datastore of the DLDP or in a data store associated with an entity. The DLDPalso can comprise or be associated with a governance platform that canfurther determine, and present to authorized users (e.g., via a userinterface), information relating to key risk indicator (KRI) metrics,which can be or can comprise risk scores relating to levels ofcompliance (e.g., levels of adherence), non-compliance (e.g.,non-adherence), or risks associated with non-compliance or potentialnon-compliance of the DLDP, its constituent or associated platforms(e.g., governance platform, rights management platform, etc.), orassociated entities, with regard to applicable laws, regulations, oragreements. Based at least in part on the various KRI metrics, riskcontrols, remediation events or actions, and/or exception events (e.g.,due to non-compliance or other data privacy or protection anomalies),the governance platform also can determine a privacy health index of anentity (e.g., organization) associated with the DLDP. Based at least inpart on tracking and analysis of the handling and use of data by theDLDP or the data stores associated with entities, and applying the setof rules with regard to the handling and use of data, the governanceplatform or the DLDP can determine non-compliance issues associated withthe DLDP, its constituent or associated platforms, or the data stores,and can remediate or facilitate remediating issues involvingnon-compliance. In accordance with various embodiments, the DLDP and/orits constituent or associated platforms can utilize artificialintelligence or machine learning to enhance various functions of orassociated with the DLDP (e.g., determining risk scores, determining aprivacy health index, determining or predicting a likelihood of anon-compliance issue occurring, etc.), as more fully described herein.

These and other aspects and embodiments of the disclosed subject matterwill now be described with respect to the drawings.

FIG. 1 illustrates a block diagram of an example, non-limiting system100 that can employ a DLDP that can desirably (e.g., efficiently oroptimally) discover and track data stored in various data stores andmanage the data, in accordance with various aspects and embodiments ofthe disclosed subject matter. The system 100 can comprise the DLDP 102that can be employed to facilitate data protection, including datasecurity and protecting data privacy, of data stored in the DLDP 102 ordata stores (e.g., database components or other data stores), such as,data store 104, data store 106, and/or data store 108, associated with(e.g., communicatively connected to) the DLDP 102 and associated with anentity or entities (not shown in FIG. 1), wherein an entity can be, forexample, an organization, a business, a company, a corporation, a user,or other type of entity. The DLDP 102 can employ a configurable designand solution that can satisfy (e.g., meet or exceed) global or regionaldata protection goals, standards, demands, or obligations of an entityor entities.

The DLDP 102 can be entity (e.g., company, organization, user, or otherentity) and environment agnostic, and can readily be employed ordeployed for use for any desired entity. The DLDP 102 also can bescalable to handle data and data protection for one or more entities andassociated amounts of data of virtually any size. For instance, the DLDP102 can be structured or designed to have a modular design anddevelopment model that can include a desirable technology stack (e.g.,cutting edge technology stack), and can have the ability to incorporatefuture technology as well.

In some embodiments, the DLDP 102 and the data stores (e.g., data stores104, 106, and/or 108) can be part of an entity datacenter 110 of orassociated with an entity (e.g., as depicted in FIG. 1). In certainembodiments, additionally or alternatively, the DLDP 102 can beassociated with one or more respective entity datacenters (e.g., entitydatacenter 110 and/or one or more other entity datacenters (not shown inFIG. 1)) associated with one or more respective data stores of one ormore respective entities. In that regard, the DLDP 102 can bemulti-tenant (e.g., can support or handle multiple entities) andmulti-lingual. For instance, the DLDP 102 can be utilized to handle dataand data protection for respective data stores of respective entities inrespective locations, and the DLDP 102 can recognize and/or identifyrespective languages of the data stored in the respective data stores ofthe respective entities, as more fully described herein.

In accordance with various embodiments, the DLDP 102 can be, can be partof, or can comprise a docker host 112 that can be or can comprise aserver component (e.g., one or more servers) on which a docker daemoncan run, wherein the server component can be or can comprise one or morephysical machines (e.g., physical or hardware servers) and/or one ormore virtual machines (VMs) that can operate as servers. The docker host112 can comprise the docker engine and can operate as an operatingsystem (OS) server where the OS and other processes can be run.

The docker host 112 can employ containerized applications, and canmanage various containers and docker images, such as docker image 114,wherein the docker images can be part of or registered with a dockerregistry 116, which can be a storage and content delivery sub-system. Inaccordance with the modular design capabilities of the DLDP 102, everymodule of the application can be deployed as a container (e.g., dockercontainer), wherein based on the infrastructure capacity of the system100, the deployment of the application can be bundled, as desired, toutilize the resources of the system 100 in a desirably efficient manner.The disclosed subject matter can enable portability via dockerizationsuch that every module of the application can be deployed as anindependent component, for example, to facilitate supporting rollingupgrades of the modules. As desired, the containers can be isolated fromeach other and can bundle their respective software, libraries, and/orconfiguration files, wherein containers can communicate with each otherthrough certain channels. The system 100, including the DLDP 102, canutilize the applications and associated containers to perform orimplement the various aspects of the disclosed subject matter, asdescribed herein.

In one embodiment, a docker image 114 can be a template that can beutilized to construct build containers. The docker image 114 cancomprise one or more files (e.g., one or more read-only or unchangeablefiles) that can have no state. The docker image 114 can also compriseone or more layers. A container can be an instantiation of a dockerimage (e.g., a run-time instantiation of a docker image). A docker pull118 can be employed to pull one or more images (e.g., docker image 114)from the docker registry 116 to facilitate instantiating one or morecontainers. For instance, using the docker pull 118, a desired dockerimage can be pulled from the docker registry 116 using a name and/or tagassociated with the docker image. A docker build 120 can be utilized tobuild images (e.g., docker image 114) from a file (e.g., docker file)and a context, wherein a context of a build can comprise one or morefiles. A docker run 122 can be utilized (e.g., executed or performed) torun respective processes in respective containers (e.g., isolatedcontainers). For instance, when a docker run 122 is utilized with regardto a container, the process for the container that runs can employ itsown file system, networking, and/or process tree, which can be desirablyisolated and separate from the docker host 112.

It is to be appreciated and understood that, while various aspects ofthe disclosed subject matter are being described with regard todocker-type implementations, the disclosed subject matter is not solimited, and, in accordance with various embodiments, the variousaspects of the disclosed subject matter, including the system 100 andDLDP 102, can be implemented utilizing other types of architectures,models, features, and/or platform as a service (PaaS) products, asdesired.

The system 100 also can include a scanner component 124 (SCANNER COMP.)that can scan data stored in the data stores 104, 106, and/or 108 tofacilitate identifying the data that is stored in the data stores 104,106, and/or 108, including identifying the data type of each item ofdata, the data format of each item of data, the language of each item ofdata, and/or other features (e.g., data attributes, data identifiers,and/or other metadata, etc.) of or associated with each item of data.The scanner component 124 can generate scan results based at least inpart on the scanning of the data stored in the data stores 104, 106,and/or 108, wherein the scan results can comprise information relatingto the data (e.g., scanned data), including information relating to thedata type, data format, language, and/or the other features of orassociated with each item of data, and/or other metadata relating to thedata. The data stored in the data stores 104, 106, and/or 108 cancomprise structured data (e.g., data contained in a relational database)and/or unstructured data (e.g., data contained in emails; image data(e.g., visual images, such as digital images, photographs, video images,or other type of image data); or other type of unstructured data). Insome embodiments, the scanner component 124 can be located locally withrespect to the DLDP 102 (e.g., as depicted in FIG. 1), whereas, in otherembodiments, one or more scanner components (e.g., scanner component124) can be deployed at or near the respective locations of respectivedata stores of the entity (e.g., organization or company) and/or one ormore other entities (e.g., other tenants). The scanner component 124 cancomprise or be associated with a classifier component (not shown inFIG. 1) that can analyze items of data scanned from the data stores 104,106, and/or 108, and, based at least in part on the results of suchanalysis, can determine or identify each item of data, including thedata type, data format, language, and/or other features of or associatedwith each item of data. In some embodiments, the DLDP 102 can employartificial intelligence or machine learning to facilitate enhancing theperformance of various aspects of the DLDP 102, including classificationof items of data by the classifier component, as more fully describedherein.

The DLDP 102 can include a transformation component 126 (TRANSFORM.COMP.) that can transform or modify data, such as data scanned from thedata stores 104, 106, and/or 108, to put such data in a desired format,for example, for presentation of the data in the desired format via auser interface component 128 (USER I/F or UI) to a user (e.g.,authorized and/or authenticated user), as more fully described herein.For instance, the transformation component 126 can receive items of datascanned from one or more of the data stores 104, 106, and/or 108. Thetransformation component 126 can analyze the items of data, and based atleast in part on such analysis, can identify respective numeric valuesof the respective items of data and/or can identify numeric valuesrelating to the respective items of data. For example, if an item ofdata is an address of a person (e.g., customer), the transformationcomponent 126 can identify the numeric characters that can represent anaddress number and/or postal code (e.g., zip code) of the address, wherethe classifier component can classify the item of data as an address ofthe person, and the transformation component 126 can transform the itemof data to facilitate presentation of the address of the person in adesirable form via the user interface component 128. As another example,if a group of items of data were scanned from a particular data set in adata store (e.g., 104), the transformation component 126 can identifythe number of items of data in the group of items of data, based atleast in part on the results of classification of the group of items ofdata by the classifier component, and can facilitate presenting thenumber of items of data in the group of items of data via the userinterface component 128.

The DLDP 102 also can comprise a secure data store 130 (e.g., privacydata store) that can desirably (e.g., securely, suitably, and/oroptimally) store desired data, such as certain items of data scannedfrom the data stores 104, 106, and/or 108 and/or information relating toitems of data stored in the data stores 104, 106, and/or 108, whereinthe information relating to the items of data can comprise scan resultsobtained from scanning the items of data, data attributes or features,and/or other metadata relating to the items of data. The secure datastore 130 can be a multi-tenant, multi-lingual data store that cansupport a data aggregation model (e.g., centralized data aggregationmodel) and can support desirably (e.g., securely, suitably, oroptimally) storing data associated with one or more desired entities(e.g., tenants), wherein data can be stored in one or more languages inthe secure data store 130.

The DLDP 102 can include a data management component 132 that can manageand secure the data stored in the secure data store 130, can manage thecompliance of the DLDP 102, its constituent or associated platforms, andthe data stores (e.g., data stores 104, 106, and/or 108) associated withthe DLDP 102 with the respective laws and regulations of the respectivejurisdictions (e.g., legal and/or geographical jurisdictions) associatedwith the DLDP 102 and data stores and with the respective agreements(e.g., contracts or SLAs) associated with the DLDP 102 and data stores,wherein the laws and regulations can relate to data protection (e.g.,data protection, privacy, and security), and wherein the agreements canrelate to data protection. The data management component 132 also canmanage various other operations and components of or associated with theDLDP 102, such as described herein. The constituent or associatedplatforms of the DLDP 102 can comprise, for example, a rights managementplatform (also referred to herein as rights management component), agovernance platform (also referred to herein as governance component),and/or another desired platform that can be utilized to facilitateproviding desirable data privacy, protection, and security. The rightsmanagement platform can manage various rights of users with regard totheir data, or information relating to their data, stored in the securedata store 130 and/or data stores (e.g., data stores 104, 106, and/or108) associated with the DLDP 102), as more fully described herein. Thegovernance platform can track and manage laws and regulations associatedwith the various jurisdictions associated with the DLDP 102, associateddata stores (e.g., data stores 104, 106, and/or 108), and associatedentities, and can track and manage agreements associated with the DLDP102, associated data stores, and associated entities, to facilitatecompliance of the DLDP 102, associated data stores, and associatedentities with applicable laws, regulations, and/or agreements, as morefully described herein.

The laws and regulations can comprise, for example, the General DataProtection Regulation (GDPR), Personal Information Protection andElectronic Documents Act (PIPEDA), Fair Credit Reporting Act (FCRA),Electronic Communications, Privacy Act (ECPA), Health InsurancePortability and Accountability Act of 1996 (HIPAA), Children's OnlinePrivacy Protection Act (COPPA), Racketeer Influenced and CorruptOrganization (RICO) Act, Family Educational Rights and Privacy Act(FERPA), U.S. Privacy Act, Medical Computer Crime Act, Federal ComputerCrime Act, Computer Fraud and Abuse Act, Video Privacy Protection Act,Digital Millenium Copyright Act (DMCA), Economic and Protection ofProprietary Information Act, California Consumer Privacy Act (CCPA),California Consumer Privacy Act, People's Republic of China (PRC)Cybersecurity Law, Phillipines Data Privacy Act, United Kingdom ComputerMisuse Act, Australia Data Privacy Act, India Information TechnologyAct, India Information Technology Rules, Japan Act on Protection ofPersonal Information Amendment, Israel Privacy Protection Law, MexicoFederal Law on the Protection of Personal Data held by PrivateProperties, and/or any other law or regulation that has been enacted orthat may be enacted through new legislation, new regulation, amendmentto a law, or amendment to a regulation.

The laws, regulations, or agreements can relate to, specify, or indicatehow data is to be handled or secured by an entity or the DLDP 102 (e.g.,based on the type of data and/or a sensitivity, privacy, or protectedstatus of data); various rights of users with regard to data of users orinformation relating thereto (e.g., information derived from, based on,or associated with the data of users); processing of data; sharing ofdata with third party entities; consents and choices of users (e.g.,user consent to receiving of emails or text messages from an entity, oruser consent to allow use of cookies by an entity, etc.); removal orunsubscription of users from receiving electronic communications; lengthof time to comply with request to remove or unsubscribe; length of timeto remedy or mitigate non-compliance with provision of a law,regulation, or agreement (e.g., safe harbor); encryption of data;security of communication channels; authentication requirements toaccess data, obtain copies of data, write data, modify data, or erasedata; anonymization of data; and/or other aspects or factors relating todata protection of data of users and information relating thereto.

In some embodiments, the DLDP 102 can comprise an applicationprogramming interface component 134 (API) that can provide variousinterfaces (e.g., APIs) that can enable desirable communication ofinformation between the secure data store 130 and the user interfacecomponent 128, the data management component 132, a notificationcomponent 136 of the DLDP 102, and/or other components of or associatedwith the DLDP 102, in accordance with various protocols and data formatssupported by the API 134.

The notification component 136 can generate and provide (e.g.,communicate) various types of notifications (e.g., notification or alertmessages) to users via the user interface component 128, as more fullydescribed herein. For example, when the DLDP 102 detects that an anomaly(e.g., data protection anomaly and/or breach) has occurred with regardto certain data of a user(s), a certain data store(s) (e.g., datastore(s) 104, 106, and/or 108), the secure data store 130, the DLDP 102,or its constituent or associated platforms (e.g., the governanceplatform or rights management platform of or associated with the DLDP102), the notification component 136 can generate a notification messagethat can notify a user (e.g., service representative of or associatedwith an entity) that the anomaly has occurred, can indicate that aremediation action is being performed to remedy or mitigate the anomaly,and/or can request that a remediation action be performed to remedy ormitigate the anomaly, wherein the anomaly can indicate non-compliance orpotential non-compliance with an applicable law, regulation, oragreement has occurred. The notification component 136 can facilitatecommunicating the notification message to the user via the userinterface component 128 to notify or alert the user that the anomaly hasbeen detected by the DLDP 102, a remediation action is being performed,and/or performance of a remediation action is requested.

In some embodiments, the system 100 comprise one or more communicationdevices, such as communication device 138, that can be a clientdevice(s) that can be associated with (e.g., communicatively connectedto) the DLDP 102 via, for example, a communication network(s) (e.g., apacket-based (e.g., an Internet protocol (IP)-based) communicationnetwork, such as the Internet, an intranet, a local area network (LAN),a wide area network (WAN), a wireless network, a core or cellularnetwork, or other type of communication network). The communicationdevice 138 can connect to the DLDP 102 via a wireline or wirelesscommunication connection or channel. A user (e.g., servicerepresentative of or associated with the entity; or user who has databeing handled by the entity) can utilize the communication device 138 tocommunicate with the DLDP 102, authenticate with the DLDP 102, requestinformation from the DLDP 102 and/or a data store (e.g., data store 104)associated with the DLDP 102, receive notifications or alerts from theDLDP 102, etc., such as more fully described herein.

Communication devices (e.g., communication device 138) can refer to orcan include, but are not limited to, for example, a computer (e.g., adesktop computer, a laptop embedded equipment (LEE), a laptop mountedequipment (LME), or other type of computer), a tablet or pad (e.g., anelectronic tablet or pad), an electronic notebook, a cellular and/orsmart phone, a mobile terminal, a mobile device, a mobile communicationdevice, user equipment (UE), a landline phone, a Personal DigitalAssistant (PDA), an electronic gaming device, electronic eyeglasses,headwear, or bodywear (e.g., electronic or smart eyeglasses, headwear(e.g., augmented reality (AR) or virtual reality (VR) headset), orbodywear (e.g., electronic or smart watch) having wireless communicationfunctionality), a media player (e.g., media player having communicationfunctionality), speakers (e.g., powered speakers having communicationfunctionality), a set-top box, an IP television (IPTV), a communicationdevice associated or integrated with a vehicle (e.g., automobile, bus,train, or ship, or other type of vehicle), a virtual assistant (VA)device, and/or any other type of communication device (e.g., other typesof Internet of Things (IoTs)).

These and other aspects and embodiments of the disclosed subject matterwill be described with regard to the other drawings and/or FIG. 1.

Referring to FIG. 2 (along with FIG. 1), FIG. 2 depicts a block diagramof an example system 200 that can utilize classification techniques, andartificial intelligence and machine learning techniques, to facilitateclassifying or identifying data scanned from data stores to facilitatedesirably (e.g., efficiently or optimally) discovering and tracking datastored in various data stores and managing the data, in accordance withvarious aspects and embodiments of the disclosed subject matter. Thesystem 200 can comprise DLDP 102, which can be employed to facilitatedata protection, including data security and protecting data privacy, ofdata stored in the DLDP 102 or data stores associated with (e.g.,communicatively connected to) the DLDP 102. The system 200 can comprisea first set of data stores, including data store 104, data store 106,and/or data store 108, associated with a first entity (e.g., firstorganization or company), and a second set of data stores, includingdata store 202, data store 204, and/or data store 206, associated with asecond entity (e.g., second organization or company). The first set ofdata stores (e.g., 104, 106, and/or 108) and the first entity can belocated in or associated with a first jurisdiction, and the second setof data stores (e.g., 202, 204, and/or 206) and the second entity can belocated in or associated with a second jurisdiction.

The DLDP 102 can comprise the secure data store 130 (e.g., privacy datastore), which can desirably store desired data, such as certain items ofdata scanned from the first set of data stores (e.g., 104, 106, and/or108), the second set of data stores (e.g., 202, 204, and/or 206), and/orinformation relating to items of data stored in the first set of datastores and/or second set of data stores, wherein the informationrelating to the items of data can comprise scan results obtained fromscanning the items of data, data attributes or data features, and/orother metadata relating to the items of data. The secure data store 130can be a multi-tenant, multi-lingual data store that can supportdesirably storing data associated with one or more desired entities(e.g., tenants), such as the first entity and second entity, whereindata can be stored in one or more languages in the secure data store130. For instance, a first set of data stored in the first set of datastores (e.g., 104, 106, and/or 108) can be in a first language, and asecond set of data stored in the second set of data stores (e.g., 202,204, and/or 206) can be in a second language. It is to be appreciatedand understood that a set of data stores (e.g., 104, 106, and/or 108)can store items of data that can be in more than one language.

The DLDP 102 can include the data management component 132 that canmanage and secure the data stored in the secure data store 130, canmanage the compliance (e.g., adherence) of the DLDP 102, its constituentor associated platforms (e.g., governance platform and rights managementplatform), and the first set of data stores (e.g., 104, 106, and/or 108)and second set of data stores (e.g., 202, 204, and/or 206) associatedwith the DLDP 102 with the respective laws and regulations of therespective jurisdictions (e.g., legal and/or geographical jurisdictions)associated with the DLDP 102 and data stores and with the respectiveagreements (e.g., contracts or SLAs) associated with the DLDP 102 anddata stores, wherein the laws and regulations can relate to dataprotection, and wherein the agreements can relate to data protection.For instance, the first set of data stores (e.g., 104, 106, and/or 108)and first entity can be associated with a first set of laws andregulations associated with (e.g., applicable to) the first jurisdictionand/or a first agreement between the first entity and anotherentity(ies) and relating to data stored in the first set of data stores.The second set of data stores (e.g., 202, 204, and/or 206) and secondentity can be associated with a second set of laws and regulationsassociated with (e.g., applicable to) the second jurisdiction and/or asecond agreement between the second entity and another entity(ies) andrelating to data stored in the second set of data stores.

In accordance with various aspects and embodiments, the system 200 cancomprise the scanner component 124, a scanner component 208, and/or ascanner component 210. The scanner component 124 can be located locallywith respect to the DLDP 102 (e.g., can be part of or in relativelyclose proximity to the DLDP 102); the scanner component 208 can bedeployed at a first location that can be in proximity to the first setof data stores (e.g., 104, 106, and/or 108); and/or the scannercomponent 210 can be deployed at a second location that can be inproximity to the second set of data stores (e.g., 202, 204, and/or 206).The scanner component 124 and/or scanner component 208 can be associatedwith (e.g., communicatively connected to) the first set of data stores(e.g., 104, 106, and/or 108). The scanner component 124 and/or scannercomponent 210 can be associated with (e.g., communicatively connectedto) the second set of data stores (e.g., 202, 204, and/or 206). In someembodiments, the scanner component 210 can be owned, managed, oroperated by the first entity, but can be located at a location inproximity to the second set of data stores.

The scanner component 124 and/or scanner component 208 can scan data(e.g., all or a desired portion of the first set of data) stored in thefirst set of data stores (e.g., 104, 106, and/or 108) to facilitateidentifying the data that is stored in the first set of data stores,including identifying the data type, the data format, the language(e.g., the first language), and/or other features (e.g., dataattributes, data identifiers, and/or other metadata, etc.) of orassociated with each item of data. The scanner component 124 and/orscanner component 208 can generate scan results based at least in parton the scanning of the data stored in the first set of data stores(e.g., 104, 106, and/or 108), wherein the scan results can compriseinformation relating to the data (e.g., data scanned from the first setof data stores), including information relating to the data type, dataformat, language, and/or the other features of or associated with eachitem of data, and/or other metadata relating to the data.

The scanner component 124 and/or scanner component 210 can scan data(e.g., all or a desired portion of the second set of data) stored in thesecond set of data stores (e.g., 202, 204, and/or 206) to facilitateidentifying the data that is stored in the second set of data stores,including identifying the data type, the data format, the language(e.g., the second language), and/or other features of or associated witheach item of data. The scanner component 124 and/or scanner component210 can generate scan results based at least in part on the scanning ofthe data stored in the second set of data stores (e.g., 202, 204, and/or206), wherein the scan results can comprise information relating to thedata (e.g., data scanned from the second set of data stores), includinginformation relating to the data type, data format, language, and/or theother features of or associated with each item of data, and/or othermetadata relating to the data.

In accordance with various aspects and embodiments, the scannercomponent 124 can comprise a classifier component 212 and languagecomponent 214, the scanner component 208 can comprise a classifiercomponent 216 and language component 218, and/or the scanner component210 can comprise a classifier component 220 and language component 222.The classifier component 212 and/or classifier component 216 can analyzeall or a desired portion of the first set of data that was scanned fromthe first set of data stores 104, 106, and/or 108. Based at least inpart on the results of the analysis, the classifier component 212 and/orclassifier component 216 can determine, identify, or classify items ofdata of the first set of data, including determining, identifying, orclassifying the data type, the data format, the language, and/or theother features of or associated with each of those items of data.Similarly, the classifier component 212 and/or classifier component 220can analyze all or a desired portion of the second set of data that wasscanned from the second set of data stores 202, 204, and/or 206. Basedat least in part on the results of such analysis, the classifiercomponent 212 and/or classifier component 220 can determine, identify,or classify items of data of the second set of data, includingdetermining, identifying, or classifying the data type, the data format,the language, and/or the other features of or associated with each ofthose items of data.

The language component 214 of scanner component 124 and/or the languagecomponent 218 of scanner component 208 can facilitate identifying ordetermining the language (e.g., first language) of the items of datascanned from the first set of data stores 104, 106, and/or 108. Thelanguage component 214 of scanner component 124 and/or the languagecomponent 222 of scanner component 210 can facilitate identifying ordetermining the language (e.g., second language) of the items of datascanned from the second set of data stores 202, 204, and/or 206. Alanguage component (e.g., 214, 218, or 222) can comprise libraries,dictionaries, or other language or grammar related information regardingvarious different languages. The languages that can be identified,determined, or recognized by the scanner component(s) (e.g., 124, 208,and/or 210) can comprise, for example, English, Spanish, French,Italian, Portuguese, Scottish Gaelic, German, Greek, Romanian,Hungarian, Chinese, Japanese, Korean, Vietnamese, Taiwanese, Thai,Indonesian, Malay, Javanese, Filipino, Tagalog, Dutch, Russian,Ukrainian, Arabic, Kurdish, Persian, Hebrew, Hindi, Bengali, Sinhala,Tamil, Turkish, Bosnian, Serbian, Croatian, African, Icelandic, Nordic,Native American languages, and/or any other desired language, and/orrespective language dialects relating thereto. A classifier component(e.g., 212, 216, or 220) can access such libraries, dictionaries orother language or grammar related information, and, based at least inpart on an analysis of items of data scanned from a data store(s) andthe information in the libraries, dictionaries or other language orgrammar related information, the classifier component (e.g., 212, 216,or 220) can determine, identify, or classify the characters (e.g.,letters, numbers, symbols, accents, punctuation, or other characters) ofeach item of data, the language of each item of data, and/or the grammarof each item of data, as well as determine, identify, or classify thedata type, data format, or other features of or associated with eachitem of data.

In some embodiments, the DLDP 102 can comprise an artificialintelligence (AI) component 224 that can utilize (e.g., apply)artificial or machine learning to facilitate enhancing the performanceof various aspects of the DLDP 102, including classification of items ofdata by the classifier component(s) (e.g., 212, 216, or 220). The AIcomponent 224 can be associated with (e.g., communicatively connectedto) the other components (e.g., secure data store 130, data managementcomponent 132, scanner component(s) (e.g., 124, 208, or 210), processorcomponent 226, or other component) of the system 200 to enable the AIcomponent 224 to communicate with such other components and facilitateperformance of operations by the system 200. The AI component 224 canemploy artificial intelligence techniques and algorithms, and/or machinelearning techniques and algorithms, to facilitate determining orinferring characters of an item of data, language of the item of data,grammar of the item of data, data type of the item of data, data formatof the item of data, or other features of or associated with the item ofdata, determining or inferring a likelihood or probability of an anomaly(e.g., non-compliance issue) occurring (e.g., within a defined amount oftime) with regard to an obligation(s) (e.g., arising out of anapplicable law, regulation, or agreement), determining or inferring alevel of compliance with an obligation(s) or a risk score with regard toa risk indicator metric (e.g., a key risk indicator (KRI) metric), aplatform (e.g., DLDP 102, governance platform, rights managementplatform, data discovery platform, data subject rights platform, thirdparty management platform, and/or notice and consents platform, etc.), adata store associated with an entity, or an entity, determining orinferring a remediation that can be performed to remedy or mitigate ananomaly, and/or automating one or more functions or features of thedisclosed subject matter, as more fully described herein.

The machine learning techniques and algorithms can comprise, forexample, a random forest technique, a linear regression technique, aregression boosting technique, a gradient boosting technique, a supportvector machine technique, a Bayesian technique (e.g., a Bayesian-type orBayesian-based technique), a k-means technique, a k-nearest neighbor(kNN) technique, a classification and regression tree technique, orother desired type of machine learning technique or algorithm. Employingthe desired machine learning technique(s) and algorithm(s), and based atleast in part on the results of analyzing items of data scanned from adata store(s) or historical information relating to data, types ofcharacters, types of languages, types of grammar, data types, dataformats, or other features of data, the AI component 224 can learn overtime to more desirably and progressively determine, identify, orclassify characters, language, grammar, data type, data format, or otherfeatures of or associated with items of data. Based at least in part onsuch learning (e.g., progressive machine learning), the performance ofthe AI component 224 and associated classifier component(s) (e.g., 212,216, or 220) can be enhanced (e.g., progressively enhanced or improved)over time with regard to classification of items of data.

In certain embodiments, additionally or alternatively, the AI component224 can employ various AI-based schemes for carrying out variousembodiments/examples disclosed herein. In order to provide for or aid inthe numerous determinations (e.g., determine, ascertain, infer,calculate, predict, prognose, estimate, derive, forecast, detect,compute) described herein with regard to the disclosed subject matter,the AI component 224 can examine the entirety or a subset of the data(e.g., data scanned from a data store(s) by a scanner component(s)(e.g., 124, 208, or 210), data stored in the secure data store 130, datain or associated with the data management component 132, data in orassociated with the processor component 226, or other data) to which itis granted access and can provide for reasoning about or determinestates of the system and/or environment from a set of observations ascaptured via events and/or data. Determinations can be employed toidentify a specific context or action, or can generate a probabilitydistribution over states, for example. The determinations can beprobabilistic; that is, the computation of a probability distributionover states of interest based on a consideration of data and events.Determinations can also refer to techniques employed for composinghigher-level events from a set of events and/or data.

Such determinations can result in the construction of new events oractions from a set of observed events and/or stored event data, whetheror not the events are correlated in close temporal proximity, andwhether the events and data come from one or several event and datasources. Components disclosed herein can employ various classification(explicitly trained (e.g., via training data)) as well as implicitlytrained (e.g., via observing behavior, preferences, historicalinformation, receiving extrinsic information, and so on) schemes and/orsystems (e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, data fusion engines, and so on)in connection with performing automatic and/or determined action inconnection with the claimed subject matter. Thus, classification schemesand/or systems can be used to automatically learn and perform a numberof functions, actions, and/or determinations.

A classifier can map an input attribute vector, z=(z1, z2, z3, z4, zn),to a confidence that the input belongs to a class, as byf(z)=confidence(class). Such classification can employ a probabilisticand/or statistical-based analysis (e.g., factoring into the analysisutilities and costs) to determinate an action to be automaticallyperformed. A support vector machine (SVM) can be an example of aclassifier that can be employed. The SVM operates by finding ahyper-surface in the space of possible inputs, where the hyper-surfaceattempts to split the triggering criteria from the non-triggeringevents. Intuitively, this makes the classification correct for testingdata that is near, but not identical to training data. Other directedand undirected model classification approaches include, e.g., naïveBayes, Bayesian networks, decision trees, neural networks, fuzzy logicmodels, and/or probabilistic classification models providing differentpatterns of independence, any of which can be employed. Classificationas used herein also is inclusive of statistical regression that isutilized to develop models of priority.

The processor component 226 can work in conjunction with the othercomponents (e.g., secure data store 130, data management component 132,scanner component(s) (e.g., 124, 208, or 210), AI component 224, or datastore 228, etc.) to facilitate performing the various functions of thesystem 200. The processor component 226 can employ one or moreprocessors, microprocessors, or controllers that can process data, suchas information relating to the DLDP 102, governance platform, rightsmanagement platform, users (e.g., users associated with items of data,users who are attempting to access items of data or information relatingto items of data), items of data scanned from data stores, laws,regulations, agreements, obligations, rules, communication devices,identifiers or authentication credentials associated with users orcommunication devices, KRI metrics, privacy principles, risk scores,privacy health index, non-compliance with obligations, notifications,alerts, remediation, data parsing, data filtering, data classification,data or user security, parameters, traffic flows, policies, defined datamanagement criteria, algorithms (e.g., data management algorithms,filtering algorithms, data classification algorithms AI algorithms,machine learning algorithms, etc., including as one or more of thesealgorithms are expressed in the form of the methods and techniquesdescribed herein), protocols, interfaces, tools, and/or otherinformation, to facilitate operation of the system 200, as more fullydisclosed herein, and control data flow between the system 200 and othercomponents (e.g., a communication device, a base station or othernetwork component or device of the communication network, data sources,or applications, etc.) associated with the system 200.

The data store 228 can store data structures (e.g., user data,metadata), code structure(s) (e.g., modules, objects, hashes, classes,procedures) or instructions, information relating to the DLDP 102,governance platform, rights management platform, users (e.g., usersassociated with items of data, users who are attempting to access itemsof data or information relating to items of data), items of data scannedfrom data stores, laws, regulations, agreements, obligations, rules,communication devices, identifiers or authentication credentialsassociated with users or communication devices, KRI metrics, privacyprinciples, risk scores, privacy health index, non-compliance withobligations, notifications, alerts, remediation, data parsing, datafiltering, data classification, data or user security, parameters,traffic flows, policies, defined data management criteria, algorithms(e.g., data management algorithms, filtering algorithms, dataclassification algorithms AI algorithms, machine learning algorithms,etc., including as one or more of these algorithms are expressed in theform of the methods and techniques described herein), protocols,interfaces, tools, and/or other information, to facilitate controllingoperations associated with the system 200. In an aspect, the processorcomponent 226 can be functionally coupled (e.g., through a memory bus)to the data store 228 in order to store and retrieve information desiredto operate and/or confer functionality, at least in part, to the DLDP102, secure data store 130, data management component 132, scannercomponent(s) (e.g., 124, 208, or 210), AI component 224, data store 228,etc., and/or substantially any other operational aspects of the system200.

Turning to FIG. 3 (along with FIGS. 1 and 2), FIG. 3 depicts a blockdiagram of an example system 300 that can illustrate a DLDP process flowin connection with the DLDP desirably (e.g., efficiently or optimally)discovering and tracking data stored in various data stores and managingthe data, in accordance with various aspects and embodiments of thedisclosed subject matter. The system 300 can comprise the DLDP 102, theuser interface component 128 (UI), the secure data store 130, and thedata management component 132. The DLDP 102 can comprise and can providevarious cloud services relating to data discovery, data tracking, datamanagement, user rights management, governance, and data protection, assuch cloud services can be provided by the first entity, which can own,manage, or operate the DLDP 102. In some embodiments, the DLDP 102 cancomprise or be part of a docker container, such as described herein.

The system 300 also can comprise the first set of data stores (e.g.,104, 106, and 108) associated with the first entity, and the second setof data stores (e.g., 202, 204, and 206) associated with the secondentity. The first set of data stores (e.g., 104, 106, and 108) can storea first set of data that can comprise data stored in databases (e.g.,relational databases), files, images (e.g., digital videos orphotographs), files, emails, and/or messages (e.g., text or multimediamessages), audio data or files, etc., associated with users (e.g., firstgroup of users). The second set of data stores (e.g., 202, 204, and 206)can store a second set of data that can comprise data stored indatabases, files, images, files, emails, and/or messages, audio data orfiles, etc., associated with users (e.g., second group of users).

The system 300 also can comprise scanner component 208 and scannercomponent 210 that can be associated with (e.g., communicativelyconnected to) the DLDP 102. The scanner component 208 can compriseclassifier component 216 and data store 302, and scanner component 210can comprise classifier component 220 and data store 304. In someembodiments, a scanner component(s) (e.g., 124, 208, and/or 210) can beor can comprise a split-post dielectric resonator (SPDR) scanner. Incertain embodiments, the first set of data stores (e.g., 104, 106, and108), the scanner component 208, and the DLDP 102 can be associated withthe first entity (e.g., owned, managed, or operated by the firstentity), and the second set of data stores (e.g., 202, 204, and 206)and/or the scanner component 210 can be associated with the secondentity.

The scanner component 208 can scan all or a desired portion of the firstset of data stored in the first set of data stores (e.g., 104, 106, and108), in accordance with the first set of laws and regulationsassociated with the first jurisdiction and/or the first agreement thatare associated with the first set of data stores, the first entity,and/or the DLDP 102. The classifier component 216 can analyze thescanned data of the first set of data to classify the scanned data togenerate first classification results, such as more fully describedherein. The scanner component 208 can store the first scan results,comprising the first scanned data, or portion thereof, first informationrelating to the first scanned data, and/or the first classificationresults, in the data store 302.

The scanner component 210 can scan all or a desired portion of thesecond set of data stored in the first set of data stores (e.g., 202,204, and 206), in accordance with the second set of laws and regulationsassociated with the second jurisdiction and/or the second agreement thatare associated with the second set of data stores, the second entity,and/or the DLDP 102. The classifier component 220 can analyze the secondscanned data of the second set of data to classify the second scanneddata to generate second classification results, such as more fullydescribed herein. The scanner component 210 can store the second scanresults, comprising the second scanned data, or portion thereof, secondinformation relating to the second scanned data, and/or the secondclassification results, in the data store 304.

With regard to the first scan results obtained by the scanner component208, the DLDP 102 can receive the first scan results from the scannercomponent 208. In certain embodiments, the DLDP 102 can comprise a batchserver component 306 that can establish a communication connection withthe scanner component 208, wherein the batch server component 306 (BATCHSERVER) can read the first scan results from the data store 302 of thescanner component 208. The batch server component 306 can be located ina highly restricted zone (HRZ) of the DLDP 102, to facilitate desirablysecuring the data. The HRZ of the DLDP 102 can be a desirably (e.g.,highly) secure area of the DLDP 102 where data of users, includingsensitive data of users, protected data of users, PII of users, and/orinformation relating to the data of users, can be desirably and securelystored (e.g., in the secure data store 130), protected, and/or processedby the DLDP 102. The DLDP 102 can desirably prevent or inhibitunauthorized access of the DLDP 102, particularly the HRZ of the DLDP102, and the data stored therein, by unauthorized users, entities, ordevices, as more fully described herein. In some embodiments, the batchserver component 306 can utilize a desired (e.g., standard) API, suchas, for example, native open database connectivity (ODBC), to facilitateestablishing the communication connection and transferring the firstscan results from the scanner component 208 to the batch servercomponent 306. The native ODBC can be an open standard API that can beutilized to facilitate accessing the data store 302 and communicatingdata (e.g., first scan results). In certain embodiments, the batchserver component 306 can be an extract, transform, load (ETL) serverthat can utilize an ETL batch process to facilitate reading andtransferring the first scan results from the scanner component 208 tothe batch server component 306.

With regard to the second scan results obtained by the scanner component210, the system 300 can employ a server component 308 (SERVER), whichcan be utilized as an intermediary server or a drop zone server that canreceive the second scan results from the scanner component 210. In someembodiments, the scanner component 210 can establish a communicationconnection with the server component 308 and can utilize a desired datatransfer process and protocol, such as, for example, a secure filetransfer protocol (SFTP) push process and protocol (SFTP also can referto secure shell protocol (SSH) file transfer protocol), to transfer thesecond scan results to the server component 308. The batch servercomponent 306 can establish a communication connection with the servercomponent 308, and can utilize a desired data transfer process andprotocol, such as, for example, an SFTP pull process and protocol, totransfer the second scan results from the server component 308 to thebatch server component 306.

The batch server component 306 can store the first scan results and thesecond scan results in the secure data store 130. The secure data store130 can be associated with, or can comprise, a server component 310(SERVER) (e.g., a database server). The server component 310 can utilizea desired (e.g., suitable or optimal) common data model to facilitatestorage of the first scan results and second scan results in the securedata store 130. The secure data store 130 also can be located in the HRZof the DLDP 102. In some embodiments, the batch server component 306 andsecure data store 130 (e.g., server component 310 of the secure datastore 130) can utilize native ODBC to facilitate establishing thecommunication connection and transferring the first scan results andsecond scan results from the batch server component 306 to the securedata store 130.

The DLDP 102 also can comprise an application server component 312 (APPSERVER) that can provide various services relating to servicing datarequests for data stored in the secure data store 130. In someembodiments, the services provided by the application server component312 can include representational state transfer (REST)ful (RESTful)services that can have a RESTful architectural style and associatedconstraints to facilitate creation of web services. The applicationserver component 312 can reside in the HRZ.

The DLDP 102 further can include a web server component 314 (WEB SERVER)that can employ a web application and provide web-related services tocommunication devices, such as communication device 138, associated with(e.g., communicatively connected to) the DLDP 102. The web servercomponent 314 can be part of or associated with the user interfacecomponent 128. The web server component 314 can be situated at a pointwithin or between the HRZ and a demilitarized zone (DMZ), which can be aperimeter network that can be a network area that can be positionedbetween the internal network of the DLDP 102 (e.g., the HRZ or otherdesirably secure internal network or area of the DLDP 102) and anexternal network, and can facilitate providing desirable isolationbetween the internal network of the DLDP 102 and the external network tofacilitate desirable security of the internal network of the DLDP 102.

When a user desires to access information regarding the first set ofdata stores (e.g., 104, 106, and/or 108) associated with the firstentity and/or the second set of data stores (e.g., 202, 204, and/or 206)associated with the second entity from the DLDP 102, the user canutilize the communication device 138 to connect to the DLDP 102 via theuser interface component 128 (e.g., via the web server component 314 ofor associated with the user interface component 128). The user and/orassociated communication device 138 can provide authenticationinformation (e.g., authentication credential(s) and/or an identifier,such as a device identifier) to facilitate authenticating the userand/or communication device 138 with the web server component 314. Theweb server component 314 can employ a desired authentication protocol(s)to authenticate the user and/or communication device 138. In accordancewith various embodiments, the web server component 314 can utilize asingle sign-on (SSO) authentication protocol, which can allow the userto log in and authenticate with the DLDP 102 using a user identification(user ID) and password, or can utilize multi-factor (e.g., two-step)authentication, which can have a user go through multiple steps,factors, or layers of authentication in order to authenticate the userand/or communication device 138 with the DLDP 102. In certainembodiments, the web server component 314 also can employ (e.g., canutilize or apply) identity and access management (IAM) policies,procedures, and technologies to facilitate ensuring that the proper(e.g., authorized) people of or associated with an entity (e.g., firstentity or second entity) have the appropriate access (e.g., access thatis authorized) to the data and resources of or associated with the DLDP102 (e.g., DLDP 102, including the secure data store 130, the first setof data stores, or the second set of data stores, etc.). In accordancewith IAM policies, the access to data and resources that is authorizedfor a person can be based at least in part on a role of that person inor in relation to an entity or can be based at least in part on anotherfactor (e.g., a subscription level of a subscription of a user with anentity).

If the user and/or communication device 138 fail to provide properauthentication information to the web server component 314, the webserver component 314 can deny the user and/or communication device 138access to the DLDP 102. If, instead, the user and/or communicationdevice 138 provide proper authentication information to the web servercomponent 314, the web server component 314 can authenticate (e.g.,approve access) to the DLDP 102, in accordance with the access levelpermitted for the user and/or communication device 138. The user, viathe communication device 138, can submit a request for data to the DLDP102 (e.g., via the user interface component 128 and web server component314). In response to the request for data, the web server component 314can initiate a secure API call to the application server component 312(e.g., can call services or API endpoints in a secure manner) using adesired authentication protocol and service. In some embodiments, theweb server component 314 can initiate the secure API call to theapplication server component 312 to facilitate authenticating the webserver component 314 with the application server component 312, whereinthe authentication can secure all communication endpoints (e.g.,hypertext transfer protocol (HTTP) endpoints) with a desired level ofauthentication. The web server component 314 also can convey (e.g.,communicate) the data request to the application server component 312.

If the application server component 312 receives proper authenticationinformation from the web server component 314, the application servercomponent 312 can authenticate the web server component 314 andassociated user and/or communication device 138 with the applicationserver component 312. In response to authenticating the web servercomponent 314 (and associated user and/or communication device 138), andin response to the data request, the application server component 312can call the server component 310 of or associated with the secure datastore 130 using a desired data access API or other suitable data accessmechanism. For example, the application server component 312 can callthe server component 310 using Java database connectivity (JDBC) and/ora close function callback (e.g., Oracle Close Callback (OCC)), whereinthe JDBC can be a Java-based data access API that can define how aclient (e.g., application server component 312) can access the servercomponent 310 (e.g., database of the server component 310).

The data management component 132 and/or server component 310 candetermine whether the data request is permitted based at least in parton the level of access granted to the user and/or communication device138, in accordance with a set of rules that can be based at least inpart on the applicable law(s), regulation(s), and/or agreement(s) (e.g.,first set of laws and regulations and/or first agreement; and/or secondset of laws and regulations and/or second agreement). In response todetermining that the data requested by the data request is permitted tobe accessed by the user and/or communication device 138, the datamanagement component 132 and/or server component 310 can determine thedata that is responsive to the data request, and can provide such datato the communication device 138 and associated user via a securecommunication channel, wherein, via the secure communication channel,the data management component 132 and/or server component 310 canforward the data to the application server component 312, which canforward the data to the web server component 314, which can forward thedata to the communication device 138. The data management component 132and/or user interface component 128 can present (e.g., display) the datain a desired format and desired user interface that can be desirable(e.g., suitable or optimal) with regard to the data requested.

Turning to FIG. 4 (along with FIGS. 1 and 2), FIG. 4 illustrates a blockdiagram of an example system 400 that can manage user data rights,governance, and data discovery with regard to data of users andinformation relating to the data of users that is stored in the DLDP orin data stores associated with the DLDP to facilitate desirablyprotecting and securing data of users and information relating thereto,in accordance with various aspects and embodiments of the disclosedsubject matter. The system 400 can comprise the DLDP 102, the userinterface component 128 of the DLDP, the secure data store 130 of theDLDP 102, the data management component 132 of the DLDP 102, and the AIcomponent 224 of the DLDP 102. The system 400 also can comprisecommunication device 138, which can be associated with (e.g.,communicatively connected to) the DLDP 102.

The data management component 132 can manage (e.g., control) scanningof, and discovery of the presence of, data of users, and informationrelating thereto, stored in data stores (e.g., the first set of datastores (e.g., 104, 106, and/or 108) or the second set of data stores(e.g., 202, 204, and/or 206), etc.) associated with entities, inaccordance with the defined data management criteria. The datamanagement component 132 can control a scanner component(s) (e.g., 124,208, or 210) to scan desired data stores (e.g., the first set of datastores (e.g., 104, 106, and/or 108) or the second set of data stores(e.g., 202, 204, and/or 206), etc.) in real time, or substantially inreal time, on a rolling basis, at periodic times, dynamically (e.g., inresponse to a condition or event), or as otherwise desired. Thefrequency or amount of scanning performed by the scanner component(s)(e.g., 124, 208, or 210) to scan respective data stores, as controlledby the data management component 132, can be based at least in part onapplicable laws, regulations, or agreements.

In accordance with various embodiments, the data management component132 can comprise a rights management component 402 and a governancecomponent 404. The rights management component 402 can be or cancomprise a rights management platform that can determine and facilitateenforcing rights of users with regard to their data and the informationrelating thereto that is stored in the secure data store 130 and/or datastores (e.g., the first set of data stores (e.g., 104, 106, and/or 108)or the second set of data stores (e.g., 202, 204, and/or 206))associated with the DLDP 102, in accordance with the set of rules andthe defined data management criteria. The rights management component402 also can manage access of the data and the information relatingthereto by users in the secure data store 130 and/or data stores (e.g.,the first set of data stores or the second set of data stores)associated with the DLDP 102, in accordance with the set of rules andthe defined data management criteria.

The rights management component 402 and/or the governance component 404can analyze the respective laws and regulations associated withrespective jurisdictions that are associated with respective users andrespective entities, and respective agreements associated withrespective users and respective entities, to facilitate determiningrespective sets of rights of respective users with regard to their dataand information relating thereto. The rights management component 402and/or the governance component 404 can determine the respective sets ofrights of respective users with regard to their data and informationrelating thereto, based at least in part on the results of such analysisof the laws, regulations, and agreements.

For example, a first law or regulation associated with a firstjurisdiction, and/or a first agreement, can provide users with a firstset of rights with regard to their data and/or information relatingthereto that is in the custody or control of entities (e.g., a firstentity's data stores or systems) associated with the first jurisdiction,wherein the first set of rights can have a first scope (e.g., a scopethat can indicate or specify how broad, extensive, or expansive each ofthe rights of the first set of rights is). A second law or regulationassociated with a second jurisdiction, and/or a second agreement, canprovide users with a second set of rights with regard to their dataand/or information relating thereto that is in the custody or control ofentities (e.g., a second entity's data stores or systems) associatedwith the second jurisdiction, wherein the second set of rights can havea second scope. Based at least in part on the results of the analysis ofthe first law and regulation, and/or first agreement, the rightsmanagement component 402 and/or the governance component 404 canidentify the first set of rights of users with regard to their dataand/or information relating thereto, the first scope of the first set ofrights, and the first obligations of entities associated with (e.g.,subject to) the first jurisdiction with regard to the first set ofrights of users. Also, based at least in part on the results of theanalysis of the second law and regulation, and/or the second agreement,the rights management component 402 and/or the governance component 404can identify the second set of rights of users with regard to their dataand/or information relating thereto, the second scope of the second setof rights of users, and the second obligations of entities associatedwith (e.g., subject to) the second jurisdiction with regard to secondset of rights of users.

The rights of users with regard to their data and/or informationrelating thereto can comprise, for example, the right of access to theirdata and/or information relating thereto, the right to information, theright to rectification, the right of erasure, the right to restrictionof processing, the right to data portability, the right to object, theright to avoid automated decision making, and/or other rights of usersthat can be specified in applicable laws, regulations, or agreements.

The right of access can allow a user to access his or her data,including personal or sensitive data, PII, and/or information relatingthereto that belongs to the user and is in possession of or is processedby an entity via the systems, data stores, etc., of the entity. Thepersonal or sensitive data can be or can comprise, for example, personaldata elements or PII of the user, wherein PII can include any data(e.g., phone number, residential or mailing address, Social Securitynumber, email address, biometric information, username, password,passcode, personal identification number (PIN), IP address, geolocationdata, social media data, or digital images, etc.) that can be used toidentify the user. The right of access also can allow the user the rightto ask an entity why and how it processes the user's data, categories ofthe data of the user involved in the data processing, who (e.g., entity,what representatives of the entity, third-party entity, etc.) has accessto the user's data, the length of time the entity intends to store theuser's data, whether the entity uses automated decision making withregard to the user's data, and/or other rights of access the user canhave with regard to their data as specified in the particular law,regulation, or agreement that provides such right of access.

The right to information can involve the right of users to informationthat an entity has to provide users when the entity is collecting data(e.g., personal or sensitive data) from users (e.g., data subjects). Forinstance, a user can have the right to inquire an entity (e.g., entitystoring or controlling data of users) what types of data (e.g., data ofor associated with users) the entity processes and why the entity wantssuch data. The right to information in a law, regulation, or agreementalso can specify when (e.g., at time of or prior to collecting the data;or within a defined time thereafter) the entity has to provide a use theinformation that is to be disclosed or provided to the user pursuant tothe right of information. The right of information can include, forexample, identity information regarding the identity of the entity,legal basis and purposes for processing the data of users,identification of the country where the processing of data will occur,identification of legitimate interests of the entity and third partyentities with regard to the data of users, identification of recipientsof data (e.g., personal or sensitive data) of users, informationregarding the intent of an entity to transfer data of users outside ofthe identified country to a third country for processing, informationregarding the data retention policy of the entity, informationexplaining the various rights of users with regard to their data,information explaining a right of the user to withdraw consent withregard to their data, tracking of activity of the user or electroniccommunications between the entity and the user, information regardingthe existence of automated decision making with regard to data of users,and/or other information relating to the right of information.

The right to rectification can provide a user with the right to modify(e.g., alter, revise, or change) their data when the user believes orfinds that their data in custody of (e.g., stored or processed by) anentity is wrong, inaccurate, out of date, or otherwise not valid. Theright to rectification also can specify how long an entity has torespond to, address, process, or complete an action relating to a user'sright to rectification when the user exercises such right (e.g., whenthe user requests that incorrect or invalid data of the user bemodified). The right of rectification also can indicate the mechanismsor ways that the entity is provide to a user in order to enable the userto exercise the right to rectification.

The right of erasure (also colloquially known as the right to beforgotten) provides a user the right to request an entity to delete data(e.g., personal or sensitive data) of the user of which the entity hascustody (e.g., data of the user that is stored in a data store of theentity). The right to erasure also can specify how long an entity has torespond to, address, process, or complete an action (e.g., deleting theuser's data) relating to a user's right to erasure when the userexercises such right (e.g., when the user requests that the user's databe deleted by the entity). The right of erasure also can indicate themechanisms or ways that the entity is provide to a user in order toenable the user to exercise the right to erasure. As part of the scopeof the right of erasure, the right of erasure also can indicate orspecify instances, situations, or circumstances under which the right oferasure does not apply, such as, for example, when the entity isrequired by applicable law or regulation to retain the data of users intheir data stores or systems for at least a defined period of time, whenretaining the data of the user is determined to be necessary for publichealth interests or in the public interest, when retaining the data ofthe user is determined to be necessary to perform preventative oroccupational medicine, or when the data of the user is being used toexercise legal claims or establish a legal defense to a legal claim.

The right to restriction of processing can provide a user the right torequest that an entity restrict processing of data of user under certainconditions. For instance, the user can exercise the right to restrictionof processing of data of the user that the user contends or believes isinaccurate, when the user objects to unlawful processing of the user'sdata, or when the entity does not have to have the user's data forprocessing, but does have to retain the user's data in its systems ordata stores by law or to enable the entity to exercise a legal claim orestablish a legal defense to a legal claim. The length of time of therestriction of processing can be temporary (e.g., for a defined orundefined period of time) or can be permanent.

The right to data portability can provide that a user have a right toobtain (e.g., obtain a copy of) the data (e.g., personal or sensitivedata) of the user that is in the custody of (e.g., stored in the systemsor data stores of or associated with) the entity, under certainconditions or circumstances. Under such certain conditions orcircumstances, the user can exercise right to data portability, forexample, to obtain the user's data for personal use or purposes, or toprovide the user's data to another entity for storage or processing. Theright to data portability also can indicate or specify a data or fileformat(s) that can or is to be utilized when providing the user's datato the user or can indicate or specify that the entity is to provide theuser's data to the user in a structured, commonly used, andmachine-readable format. The right to data portability also can specifyhow long an entity has to respond to, address, process, or complete anaction relating to a user's right to data portability when the userexercises such right to request that the entity provide the user's datato the user or another entity.

The right to object can allow a user to object to the processing of dataof the user, including profiling, by an entity, under certain conditionsor circumstances. For instance, the user can exercise the right toobject to processing of the user's data by the entity when theprocessing of the user's data relates to direct marketing to the user(e.g., entity sending marketing emails to the user). The right to objectalso can specify how long an entity has to respond to, address, process,or complete an action relating to a user's right to object when the userexercises such right (e.g., can specify how long the entity has to ceasesending marketing emails to the user). The right to object (or anotherright of the user) can indicate or specify that the entity has todisclose the user's right to object (and/or disclose the other rightsthe user has) to the user (e.g., in a privacy policy statement).

The right to avoid automated decision making can provide a user theright to not be subject to a decision of the entity based solely onautomated processing or decision making, including profiling, exceptunder certain circumstances, as defined by law, regulation, oragreement. As part of exercising the right to avoid automated decisionmaking, the user can request to have human intervention to have a humanuser (e.g., human representative of or associated with the entity)intervene and interact with the user.

In addition to or as an alternative to these rights of users, dependingon the applicable law, regulation, or agreement, a user can have certainother rights relating to the use, storage, or processing of the user'sdata by an entity, consent (e.g., explicit or implicit consent) orwithdrawal of consent with regard to the user's data or electroniccommunications between the entity and the user, and personalization ofthe user's data or of the user by the entity, etc.

The rights management component 402 or governance component 404 canmonitor and track the exercising of the various rights of users by usersand the responses or actions taken by entities in response to theexercising of the various rights of users by users. Based at least inpart on the monitoring and tracking, the rights management component 402or governance component 404 can determine whether respective entitiesare desirably (e.g., suitably, sufficiently, or acceptably) complyingwith the respective sets of rights of respective users, in accordancewith respective applicable laws, regulations, or agreements, as morefully described herein.

With further regard to the governance component 404, the governancecomponent 404 (e.g., governance platform) can determine and enforce theset of rules, which the governance component 404 can determine based atleast in part on respective laws and regulations of respectivejurisdictions and/or respective agreements, in accordance with thedefined data management criteria, as more fully described herein. Thegovernance component 404 also can determine levels of compliance (e.g.,with laws, regulations, or agreements) and/or risk scores for or withregard to KRI metrics, the DLDP 102, the rights management platform, thegovernance platform, another platform, a set of data stores (e.g., thefirst set of data stores (e.g., 104, 106, and/or 108) or the second setof data stores (e.g., 202, 204, and/or 206)), and/or an entity (e.g.,the first entity or the second entity), etc., as more fully describedherein.

In some embodiments, the rights management platform 402 and thegovernance component 404 can be part of the DLDP 102. In otherembodiments, the rights management platform 402 and/or the governancecomponent 404 can be separate from and associated with (e.g.,communicatively connected to) the DLDP 102.

Referring to FIG. 5 (along with FIGS. 1, 2, and 4), FIG. 5 presents adiagram of an example user interface 500 relating to example data thatcan be presented to a user by the DLDP 102 in response to a datarequest, in accordance with various aspects and embodiments of thedisclosed subject matter. For instance, a user can desire to view orobtain certain data associated with the first entity and stored in thefirst set of data stores (e.g., 104, 106, and/or 108) associated withthe first entity. The user, using communication device 138, canauthenticate with the DLDP 102, as more fully described herein. Inresponse to being authenticated by the DLDP 102, the rights managementcomponent 402 can determine what access rights the user and/orcommunication device 138 is permitted to have to access data trackedand/or managed by the DLDP 102 in the secure data store 130 and datastores (e.g., the first set of data stores (e.g., 104, 106, and/or 108))associated with the DLDP 102, based at least in part on theauthentication information provided by the user and/or communicationdevice 138, a role of the user with or in relation to the first entity,and/or another desired factor. The rights management component 402 cangrant the user and/or communication device 138 a set of access rights,in accordance with the determination regarding the access rights theuser and/or communication device 138 is permitted to have.

The user, via the communication device 138, can submit a data request torequest certain data. Example user interface 500 can be example resultsto the data request. The example user interface 500 can comprise a datamap 502 that can provide information regarding data associated with thefirst entity, as stored in the first set of data stores (e.g., 104, 106,and/or 108), or portion thereof, and/or the secure data store 130, aspart of data discovery 504 of the DLDP 102. The data map 502 can provideinformation regarding, for example, the systems 506 of or associatedwith the first entity, data stores 508 for each of the systems 506, datasets 510 for each of the data stores 508, and columns 512 for each ofthe data sets 510 (e.g., as such information has been filtered by theselected filters, such as described herein). With regard to each system,such as SYSTEM A 514, of the systems 506, the DLDP 102 can provideinformation regarding the number of personal data elements 516 (e.g.,3970 personal data elements) and the number of data stores 518 (e.g., 36data stores) in which those personal data elements are stored. Withregard to each data store, such as DATA STORE A 520, of the data stores508, the DLDP 102 can provide information regarding the number ofpersonal data elements 522 (e.g., 1065 personal data elements) and thenumber of data sets 524 (e.g., 15 data sets) in which such personal dataelements are stored. With regard to each data set, such as DATA SET A526, of the data stores 508, the DLDP 102 can provide informationregarding the number of personal data elements 528 (e.g., 15 personaldata elements) that are stored in that data set. The columns 512 portionof the user interface 500 can present various personal data elements,such as, for example, account number 530, birth date 532, and/orcitizenship 534, etc. Other types of personal data elements (e.g., PIIelements or personal attributes) can include, for example, full name(e.g., first name, last name, and/or maiden name), phone number (e.g.,day phone number, home phone number, work phone number, and/or cellphone number), home address, work address, email address, SocialSecurity Number, passport number, driver's license number or othergovernment ID number, financial information (e.g., bank or creditaccount information, loan information, income information, or wealthinformation, etc.), age, education, gender, race, ethnicity, nationalorigin, religion, genetic information, health information, politicalaffiliation, trade union membership, location information, transactionhistory information, marital status information, family information,communication services provider (e.g., Internet service provider), login or authentication information, biometric information, and/or otherdesired information regarding users or entities.

The user interface 500 also can present information indicating theoverall number of personal attribute columns 536 (e.g., 49527 personalattribute columns (or personal data element columns)) contained in thesystems 506 (e.g., as such information has been filtered by the selectedfilters, such as described herein). The data management component 132can facilitate presenting various types of filters 538 to the user viathe user interface 500, and the user can apply desired filters to theinformation to filter out undesired information. For instance, as shownin the example user interface 500, there can be a zone filter 540 thatcan filter the information by zone(s). In the example user interface500, a filter for ZONE A has been applied to filter the information toinclude information relating to ZONE A. Also, as shown in the exampleuser interface 500, there can be a source filter 542 that can filter theinformation by source(s) of the information. In the example userinterface 500, a filter for SOURCE A has been applied to filter theinformation to include information relating to SOURCE A. Further, asshown in the example user interface 500, there can be a business unitfilter 544 that can filter the information by business unit(s)associated with the information. In the example user interface 500, anall filter for all business units has been applied to filter theinformation to include information relating to all of the businessunits.

In some embodiments, the user interface 500 can present personal dataattributes filters 546, which can be presented in a desired form, suchas, icons, as depicted in the user interface 500. Respective icons canrepresent respective types of personal data attribute filters. Incertain embodiments, the icons of the personal data attributes filters546 can be colored, highlighted, or modified to represent differenttypes of information or different types of information statuses (e.g.,data privacy status or attribute). For example, sensitive personal datacan be represented by a first color 548 to indicate that the personaldata is considered to be sensitive, non-sensitive data can berepresented by a second color 550 to indicate that such personal data isconsidered to be non-sensitive, and/or protected data can be representedby an icon modified to have a lock 552 to indicate that such personaldata can be protected personal data. In the example user interface 500,the birth date filter icon 554 can have the second color 550 to indicatethat birth date information regarding users is considered to benon-sensitive; the birth date filter icon 554 can have the second color550 to indicate that birth date information regarding users isconsidered to be non-sensitive; the marital status filter icon 556 canhave the first color 548 to indicate that marital status informationregarding users is considered to be sensitive; and the biometricinformation filter icon 558 can have the first color 548 and a lock toindicate that biometric information regarding users is considered to besensitive and protected personal data. It is to be appreciated andunderstood that different types of data can be considered to besensitive, non-sensitive, or protected data based at least in part onapplicable laws, regulations, and/or agreements, and/or as desired bythe entity (as permitted by the applicable laws, regulations, and/oragreements), in accordance with the defined data management criteria.

To apply one or more filters to the information, the user can select oneor more desired filters and press the apply button 560 to apply the oneor more filters to the information. To remove or clear filters, the usercan select the clear button 562 to remove or clear any filters that hadbeen applied to the information.

As also can be observed in the example user interface 500, in accordancewith various aspects and embodiments, as desired, and when in accordancewith the set of access rights granted to the user, the user can accessinformation regarding functional usage 564, which can indicate thefunctions of the DLDP 102 or system that the user has access rights toaccess and/or that the user is utilizing, and/or the user can accessinformation regarding risk scores 566, which can indicate the riskscores (e.g., risk levels or ratings) of various parts of the system(e.g., risk scores of KRI metrics, risk score of the DLDP 102, riskscore of the access rights platform, risk score of the governanceplatform, and/or risk score for the third party management platform,etc.).

The example user interface 500 also can enable the user, when inaccordance with the set of access rights, to view an overview 568 of theinformation associated with the first entity that is tracked and managedby the DLDP 102, a landscape 570 of the physical and/or logicalrelationships between various systems, data stores, databases, datasets, and/or other data layers or types associated with the firstentity. The example user interface 500 also can enable the user, when inaccordance with the set of access rights, to view information relatingto consents 572 of users including information regarding types ofconsents that can be given by users and/or types of consents that havebeen given by users with regard to data (e.g., personal data) of users.

Turning to FIGS. 6 and 7 (along with FIGS. 1, 2, and 4), FIG. 6 presentsa diagram of an example user interface 600 relating to example data thatcan be presented in a first language to a user by the DLDP 102 inresponse to a data request, and FIG. 7 presents a diagram of an exampleuser interface 700 relating to example data that can be presented in asecond language to a user by the DLDP 102 in response to a data request,in accordance with various aspects and embodiments of the disclosedsubject matter. In the example user interface 600, in response to a datarequest from the user, and when in accordance with the set of accessrights granted to the user by the rights management component 402, thedata management component 132 can determine and generate the exampledata in the first language (e.g., English) and can present the exampledata via the user interface 600. For instance, based on the datarequest, the data management component 132 can generate a scan overview602 associated with the first entity and relating to the scanningperformed of the systems, including the first set of data stores (e.g.,104, 106, and/or 108), associated with the first entity. The scanoverview 602 can include an overall risk score 604 (e.g., 25/100, lowrisk) associated with the first entity (e.g., associated with thesystems, data stores, or data, etc.) associated with the first entity,and other information, such as, for example, information relating to thenumber of environments 606, information relating to the number ofdatabases 608, information relating to the number of tables containingPII 610, information relating to the number of data sources 612,information relating to the number of tables 614, and informationrelating to the number of PII columns 616, as all such information wasdiscovered as a result of scanning of the systems, data stores, etc., bythe scanner component (e.g., 124 or 208).

Also, based on the data request, the data management component 132 candetermine and generate a scan trend 618 over a defined period of time(e.g., last 12 months) of the scanning of the systems, data stores,etc., associated with the first entity, where the scan trend 618 canindicate the coverage 620 of the scanning at given times (e.g., eachmonth) over the defined time period, the amount of sensitive data 622discovered through scanning at the given times, and the core PII 624discovered through scanning at the given times, as well as the totalnumber of items of core PII 626 and total number of items of sensitivedata 628 discovered through scanning over the defined time period.

The data management component 132 also can determine and generate a scancoverage 630 that can indicate the percentage of tables associated withthe first entity that have been scanned and the percentage of tablesassociated with the first entity for which scanning is still pending.Further, as desired, in response to the data request, the datamanagement component 132 can determine and generate a data distributionby geography 632 that can provide information regarding the distributionof sensitive data, core PII, number of data sources, etc., pergeographical region (e.g., continent, country, state, territory, orprovince, etc.), with regard to the first entity. Also, as desired, inresponse to the data request, the data management component 132 candetermine and generate information relating to sensitive data categories634 that, for each of desired categories of sensitive data, can indicatea distribution of each such type of sensitive data and/or a number ofitems of each such type of sensitive data.

With regard to the example user interface 700 of FIG. 7, the datamanagement component 132 can present the same example data as presentedin the example user interface 600 of FIG. 6, except that the datamanagement component 132 can generate the example data in a secondlanguage (e.g., Spanish), and can present the example data in the secondlanguage in the example user interface 700 to the user. The languagethat the data management component 132 utilizes to present theinformation to the user via a user interface (e.g., user interface 600,or user interface 700, etc.) can be determined by the data managementcomponent 132 based at least in part on the language employed in thedata as it is collected through scanning, a language preference of theuser, a location of the user, and/or another desired factor. Forexample, if the language of the data was in Spanish as it was scannedfrom the systems, data stores, etc., associated with an entity, the datamanagement component 132 can present the data, or portion thereof, orinformation relating to or based on the data, in Spanish in a userinterface. As another example, alternatively, if there is a userpreference to have information conveyed in a first language (e.g.,English), and the data is in a second language (e.g., Spanish) when itis scanned from the systems, data stores, etc., associated with anentity, based on the user preference, the data management component 132can translate the data, or portion thereof, or information relating toor based on the data, from the second language to the first language,and can present the data and/or associated information in the firstlanguage in the user interface to the user.

Referring to FIG. 8 (along with FIGS. 1, 2, and 4), FIG. 8 depicts adiagram of an example user interface 800 that can comprise informationrelating to data collection with regard to data associated with anentity, in accordance with various aspects and embodiments of thedisclosed subject matter. The data management component 132 candetermine and generate the data presented in the user interface 800 inresponse to a request from a user (e.g., authorized and/or authenticateduser), and in accordance with a set of access rights that can be grantedto the user based at least in part on a set of rules, in accordance withthe defined data management criteria. For instance, in response to thedata request, and based at least in part on a results of the scanning ofthe data from the systems, data stores (e.g., 104, 106, and/or 108),data, etc., associated with the first entity, and an analysis of suchdata, the data management component 132 can determine and generateinformation regarding the PII collected by all channels 802, which caninclude, for example, the percentage of the PII that was collected bythe DLDP 102 via API, the percentage of the PII obtained by the DLDP 102via file transfer, and the percentage of PII obtained by the DLDP 102via email.

Also, based at least in part on the results of the data scanning, andthe analysis of such data, the data management component 132 candetermine and generate information regarding PII collected by allbusiness functions 804 associated with the first entity, including, forexample, information regarding PII collected by onboarding, compliance,customer success operations (CS-OPS), marketing, and risk, wherein, foreach business function, the information regarding such PII can beaggregated or broken down by the amount or percentage of PII collectedby channel (e.g., API, file transfer, or email).

As desired, and based at least in part on the results of the datascanning, and the analysis of such data, the data management component132 also can determine and generate information regarding PII attributes806 for PII collected by all business functions associated with thefirst entity, including, for example, information regarding PIIcollected by name, contact number, address, email gender, and date ofbirth (DOB), and/or can indicate which types of PII (e.g., genderinformation) are considered sensitive information (e.g., by using acolor code or other type of emphasis to indicate the type of informationis sensitive information).

In connection with data collection, the DLDP 102 can enable the user toapply desired filters 808 to filter the data collection to have the DLDP102 collect desired data based at least in part on one or more selectedfilters. For instance, as presented in the example user interface 800,the DLDP 102 can enable filtering by process 810 (e.g., process of datacollection) or PII 812, method 814 of data collection (e.g., method orchannel of data collection, such as, for example, API, file transfer, oremail, etc.), boundary 816 of the data collection (e.g., internal orexternal), business function 818, and PII attributes 820. The applybutton 822 can be utilized to apply the selected filters, and the clearbutton 824 can be utilized to clear any filters that had been applied.As depicted in the example user interface 800, process 810 has beenselected, API has been selected as the method, the boundary that isselected is internal, the business function that is selected isonboarding, and there are four PII attributes selected. Based at leastin part on the selected filters, the DLDP 102 can filter the collecteddata to present filtered information 826 comprising informationregarding onboarding with regard to the four selected PII attributes,name 828, email 830, biometrics 832, and rewards 834, wherein theinformation regarding name 828 and email 830 can be non-sensitiveinformation, and wherein the information regarding biometrics 832 andrewards 834 can be sensitive information. The user can select a PIIattribute(s) (e.g., name 828, email 830, biometrics 832, or rewards 834)in the user interface 800 to obtain further information (e.g., to drilldown to see additional information) regarding the selected PIIattribute(s).

Turning to FIG. 9 (along with FIGS. 1, 2, and 4), FIG. 9 illustrates adiagram of an example user interface 900 that can comprise informationrelating to access of data and access controls to control access to dataassociated with an entity, in accordance with various aspects andembodiments of the disclosed subject matter. The data managementcomponent 132 can determine and generate the data presented in the userinterface 900 in response to a request from a user (e.g., authorizedand/or authenticated user), and in accordance with a set of accessrights that can be granted to the user based at least in part on a setof rules, in accordance with the defined data management criteria. Thedata management component 132 (e.g., the rights management component 402of the data management component 132) can track the accessing of data,including personal, sensitive, and/or protected data of customers,associated with the first entity by users (e.g., users of or associatedwith the first entity, or users associated with a third party entity,etc.) and access controls implemented on the data, and can determinewhether appropriate access controls have been implemented to desirably(e.g., sufficiently) protect the data of customers, particularly thepersonal, sensitive, and/or protected data of the customers. The datamanagement component 132 can provide details regarding, for example, thenumber of users who have performed read operations, write operations, ordelete operations on data (e.g., personal, sensitive, and/or protecteddata) of customers across the various systems, data stores (e.g., 104,106, and/or 108), etc., associated with the first entity and whethersuch read operations, write operations, or delete operations wereappropriate or not (e.g., whether such access to data and suchoperations by the users were permitted based at least in part on theapplicable laws, regulations, and/or agreements).

For instance, in response to a data request from the user, and based atleast in part on a results of the scanning of the data from the systems,data stores (e.g., 104, 106, and/or 108), data, etc., associated withthe first entity by the scanner component (e.g., scanner component 124or 208), and an analysis of such data, the data management component 132can determine and generate information regarding the role and user count902 of the users who accessed the data or performed operations on thedata, and can present such information regarding the role and user count902 to the requesting user via the example user interface 900. Theinformation regarding the role and user count 902 can indicate, forexample, the number of individual users who have accessed the dataand/or performed operations on the data over a defined period of time,the number of systematic data accesses or data operations that have beenperformed, the respective roles (e.g., full-time employee of the firstentity, or a user who is under contract with the first entity) of theindividual users who have accessed the data in the systems, data stores,etc., associated with the first entity.

Also, based at least in part on the results of the data scanning by thescanner component (e.g., scanner component 124 or 208), and the analysisof such data, the data management component 132 can determine andgenerate information regarding unique PII access 904 of data (e.g., PII)of users by business unit (BU), such as BU1, BU2, BU3, etc., andinformation regarding non-accessed tables 906 in the first set of datastores (e.g., 104, 106, and/or 108) to indicate which tables in the datastores have not been accessed over different time periods (e.g., in thelast 3 months, last 6 months, last year, and last two years).

Further, in connection with presenting information regarding data accessand access controls, the DLDP 102 can enable the user to apply desiredfilters 908 to filter information relating to data access and accesscontrols to have the DLDP 102 present desired (e.g., filtered) databased at least in part on one or more selected filters. For instance, aspresented in the example user interface 900, the DLDP 102 can enablefiltering by zone 910 (e.g., HRZ, DMZ, or HRZ-DMZ), data source 912,system 914 of the first entity, business unit 916 of the first entity(e.g., the whole organization of the first entity, or one or moreparticular business units of the organization), and personal dataattributes 918. The apply button 920 can be utilized to apply theselected filters, and the clear button 922 can be utilized to clear anyfilters that had been applied. As depicted in the example user interface900, for zone 910, HRZ has been selected, for data source 912, Oraclehas been selected, for system 914, Oracle has been selected, and forbusiness unit 916, payments has been selected.

The data management component 132 can filter the information based atleast in part on the selected filters. In accordance with the filters,the data management component 132 can present the filtered information,which can include, the system level information 924 and the data mapping926. The system level information 924 can comprise, with regard to thepayments business unit, the user count 928, which can indicate thenumber of users who have accessed the data or performed operations overthe defined time period, the role count 930, which can indicate thenumber of roles associated with the users, and the privilege number 932,which can indicate the number of privileges over the defined timeperiod. The information relating to the data mapping 926 can include,with regard to the payments business unit, information relating toprivileges 934, and information relating to read operations 936, writeoperations 938, and delete operations 940 performed by users, whereinthe operations information can comprise the number of operations or moredetailed information regarding such operations (e.g., by selecting readoperations 936, write operations 938, or delete operations 940). Theinformation relating to the data mapping 926 also can compriseinformation relating to the databases 942 that contain informationassociated with the payments business unit and were accessed by users.The information relating to the data mapping 926 further can includeinformation relating to the business units 944 associated with thepayments business unit, roles information 946 relating to roles of userswho accessed data relating to the payments business unit, andinformation relating to unique PII instances 948 associated with thepayments business unit and data accessed by users, wherein theinformation relating to unique PII instances 948 can comprise the numberof unique PII instances or more detailed information regarding suchunique PII instances.

Turning to FIG. 10 (along with FIGS. 1, 2, and 4), FIG. 10 depicts adiagram of an example user interface 1000 that can comprise informationrelating to data sharing of data associated with an entity with thirdparty entities, in accordance with various aspects and embodiments ofthe disclosed subject matter. The data management component 132 candetermine and generate the information presented in the user interface1000 in response to a request from a user (e.g., authorized and/orauthenticated user), and in accordance with a set of access rights thatcan be granted to the user based at least in part on a set of rules, inaccordance with the defined data management criteria. The datamanagement component 132 (e.g., the rights management component 402 ofthe data management component 132) can track the accessing and sharingof data, including personal, sensitive, and/or protected data ofcustomers, associated with the first entity with third party entities,and can determine whether the data shared with the third party entitieswas only for permitted purposes, in accordance with applicable laws,regulations, agreements (e.g., SLA or vendor agreement), and/or notices(e.g., notices provided to users regarding the sharing of data of userswith third party entities).

In response to a data request relating to third party data sharing thatis received from the user, and based at least in part on a results ofthe scanning of the data from the systems, data stores (e.g., 104, 106,and/or 108), data, etc., associated with the first entity by the scannercomponent (e.g., scanner component 124 or 208), and an analysis of suchdata, the data management component 132 can determine and generateinformation regarding third party assessments 1002, which can includeinformation regarding, for example, information security (INFOSEC), riskor impact assessments (e.g., privacy impact assessment (PIA)), process,and/or records and information governance (RIG), and can indicatewhether such information is with assessment or without assessment. Thedata management component 132 also can determine and generateinformation regarding third party metrics 1004, which can includeinformation regarding outbound data sharing (e.g., data outbound fromthe first entity to third entities), such as, for example, the number ofrelationships of the first entity with third party entities, the PIIunique count, and/or the number of countries (e.g., countries wherethird party entities are located). The data management component 132 canpresent such information regarding third party metrics 1004 to therequesting user via the user interface 1000.

In response to the data request, the data management component 132further can determine and generate information regarding PII—third partycount 1006, which can comprise information regarding respective types(e.g., attributes) of personal data of users (e.g., customers) and thenumber of third party entities with which the respective types ofpersonal data have been shared. The personal data of users (e.g., name,address, account number, or email address, etc.) can be indicated asbeing sensitive data or non-sensitive data, for example. The datamanagement component 132 can present such information regardingPII—third party count 1006 to the requesting user via the user interface1000.

Further, in connection with presenting information regarding data accessand access controls, the DLDP 102 can enable the user to apply desiredfilters 1008 to filter information relating to data sharing with thirdparty entities to have the DLDP 102 present desired (e.g., filtered)data based at least in part on one or more selected filters. Forinstance, as presented in the example user interface 1000, the DLDP 102can enable filtering by whether the data has been scanned 1010 (e.g.,scanned or not scanned), inbound or outbound 1012, customer region 1014(e.g., by continent, country, state, province, district, or other regionor jurisdiction), channel 1016 of sharing of data (e.g., API, filetransfer, or other channel), third party category 1018 (e.g.,operational services, marketing and public relations, paymentprocessors, or legal, etc.), assessment 1020, and personal dataattributes 1022. The apply button 1024 can be utilized to apply theselected filters, and the clear button 1026 can be utilized to clear anyfilters that had been applied. As depicted in the example user interface1000, for scanned 1010, scanned has been selected to indicate theinformation was scanned from the systems, data stores, etc., associatedwith the first entity, for inbound outbound 1012, outbound has beenselected to indicate filtering information to include information thatwas shared outbound from the first entity to third party entities, forcustomer regions 1014, five customer regions have been selected, forchannel 1016, three channels have been selected, for third partycategory 1018, twelve third party categories have been selected, and forassessment 1020, five assessments have been selected. In someembodiments, the user interface 1000 can include a download button 1028that can be selected by the user to download the information (e.g.,filtered information) relating to data sharing with third partyentities.

The data management component 132 can filter the information based atleast in part on the selected filters. In accordance with the filters,the data management component 132 can present the filtered information,which can comprise, for example, third party names 1030 (e.g., thirdparty A, third party B, or third party C, etc.), contract status 1032(e.g., active, inactive, or unknown) to indicate the respective contractstatuses of the third party entities with the first entity, category1034, which can indicate the respective categories (e.g., operationalservices, marketing and public relations, payment processors, or legal,etc.) of the relationships of the third party entities with the firstentity, and customer region 1036, which can indicate the respectiveregions (e.g., Americas, including, for example, North America, CentralAmerica, and South America; Europe, Middle East, and Africa (EMEA); orAsia Pacific (APAC); etc.) covered by the third party entities. The datamanagement component 132 can present such information (e.g., filteredinformation) regarding third party names 1030, contract status 1032,category 1034, customer region 1036, and/or desired filtered informationto the requesting user via the user interface 1000.

In some embodiments, the user interface 1000 can provide a searchfunction 1038 that can enable the user to enter search terms (e.g.,third party name or code or other desired search term) to filterinformation based at least in part on the search terms entered into thesearch function 1038. Based at least in part on the search terms enteredin the search function 1038 and/or the filters 1008 selected, the datamanagement component 132 can filter the information (e.g., informationrelating to data sharing with third party entities) to present desiredfiltered information in the user interface 1000 or another userinterface associated with (e.g., user interface that can be accessed viaselection of a button on) the user interface 1000.

While enabling a requestor (e.g., user, entity, or device) to use thesearch function 1038 and search terms to search for data of a user(s)(e.g., the requesting user or another user), the data managementcomponent 132 can desirably (e.g., to a high degree, suitably, oroptimally, etc.) secure and protect data of the user(s), and/orinformation relating thereto, that is stored in the secure data store130 or in a data store (e.g., data store(s) 104, 106, and/or 108)associated with the DLDP 102, in accordance with the defined datamanagement criteria, the corresponding set of rules, and/orcorresponding applicable law, regulation, agreement, and/or consent ofthe user. For instance, if a requestor (e.g., requesting user, entity,or device) attempts to access data of a user (e.g., the requesting useror another user) and/or information relating thereto, using the searchfunction 1038 or otherwise, the data management component 132 candetermine what data of the user or related information (if any), and/orwhat type(s) of data (e.g., non-sensitive or non-protected data,personal or sensitive data, protected data, and/or PII, etc.) or relatedinformation, the requestor is authorized to access, based at least inpart on the identity or role of the requestor, and/or the authenticationinformation of the requestor, and based at least in part on the set ofrules. The data management component 132 can allow the requestor toaccess to only such data of the user or related information stored inthe secure data store 130 and/or data store(s) (e.g., data store(s) 104,106, and/or 108) associated with the DLDP 102 that the requestor ispermitted to access, and can prevent the requestor from accessing otherdata of the user or related information in the secure data store 130and/or data store(s) that the requestor is not permitted to access,based at least in part on the set of rules.

In some instances, a requestor may be permitted to access certain dataof a user in the secure data store 130 or in a data store (e.g., datastore(s) 104, 106, and/or 108) associated with the DLDP 102 only under(e.g., subject to) certain restrictions. In such instances, the datamanagement component 132 can enforce the restrictions (e.g., can enforcea rule(s) of the set of rules relating to such restrictions) to allowthe requestor to only access the certain data of the user in accordancewith the applicable restrictions. For example, an item of data of theuser may be restricted to be read-only or view-only with regard to therequestor, and the data management component 132 can enforce suchrestriction to only allow the requestor to view the item of data, butcan restrict or prevent the requestor from overwriting, editing,deleting, erasing, downloading, or printing the item of data. Thus, thedata management component 132 can maintain desirable (e.g., a high levelof, suitable, applicable, or optimal, etc.) security of the data ofusers and information relating thereto that is stored in the secure datastore 130 or in a data store (e.g., data store(s) 104, 106, and/or 108)associated with the DLDP 102 to prevent or inhibit unauthorized access,sharing, or use of the data of users and the information relatingthereto, in accordance with the defined data management criteria and thecorresponding set of rules, which can be based at least in part onapplicable law, regulation, agreement, and/or consent of the user.

Referring to FIG. 11 (along with FIGS. 1, 2, and 4), and with furtherregard to governance of the DLDP 102, the secure data store 130, andassociated systems, data stores, data, etc., of entities associated withthe DLDP 102 by the governance component 404, FIG. 11 illustrates ablock diagram of an example system 1100 that can employ a governancecomponent to facilitate governing the DLDP 102 and associated systems,data stores, data, etc., of entities, data sharing, and compliance withlaws, regulations, and agreements, in accordance with various aspectsand embodiments of the disclosed subject matter. The system 1100 cancomprise the governance component 404 that can perform variousgovernance-related operations to facilitate determining whether the DLDP102 and associated systems, data stores, data, etc., associated withentities are in compliance (e.g., adherence) with applicable laws,regulations, and/or agreements, and/or to facilitate ensuring desirable(e.g., suitable, acceptable, or optimal) compliance of the DLDP 102 andthe associated systems, data stores, data, etc., associated with theentities with the applicable laws, regulations, and/or agreements, inaccordance with the defined data management criteria, such as more fullydescribed herein. The governance component 404 can facilitate managingthe DLDP 102, secure data store 130, and/or the associated systems, datastores, data, etc., associated with the entities with regard to, forexample, data discovery-related issues (e.g., issues discovered fromscanning of systems, data stores, data, etc., associated with entities),data subject rights (DSR) request-related issues (e.g., issue relatingto whether a requesting user gained improper access to data),consent-related issues (e.g., issues relating to consent to receiveemails, issues relating to consent to collect data of users, and/orissues relating to consent to share data of users, etc.), and/or thirdparty-related issues (e.g., issues relating to whether sharing of dataof a user(s) with third party entities is or was permitted by anapplicable law, regulation, agreement, and/or consent of the user(s)).

The governance component 404 can comprise a front end 1102 and a backend 1104. The front end 1102 of the governance component 404 can performcertain governance-related operations (e.g., determining rules relatingto laws, regulations, and/or agreements, determining compliance with therules, determining if and when anomalies, such as non-compliance withthe rules occur, determining risk scores, or determining a privacyhealth index, etc.). The back end 1104 of the governance component 404can perform other types of governance-related operations (e.g.,generating or processing exception messages relating to non-compliance,performing or facilitating performing remediation actions in response toexception messages, or notifying when remediation actions have beencompleted, etc.).

The front end 1102 of the governance component 404 can comprise aningestion component 1106 that can monitor and track information relatingto respective laws and regulations associated with respectivejurisdictions and respective agreements associated with respectiveentities. For instance, in connection with monitoring and tracking suchinformation, the ingestion component 1106 can receive respective lawsand regulations (e.g., GDPR, HIPAA, COPPA, FCRA, ECPA, FERPA, PIPEDA,CCPA, PRC Cybersecurity Law, India Information Technology Act, IndiaInformation Technology Rules, and/or other laws or regulations) relatingto data protection and associated with respective jurisdictions, orother information relating thereto, and can continue to monitor andtrack for any updates (e.g., modifications or changes) made to any lawsand regulations. The ingestion component 1106 also can receiverespective agreements relating to data protection and associated withentities and/or the DLDP 102, or information relating thereto, and cancontinue to monitor and track for any updates made to any agreements.

Based at least in part on the laws and regulations, agreements, andother information relating thereto, the governance component 404 candetermine a set of rules relating to data protection of data associatedwith the DLDP 102 and systems, data stores (e.g., 104, 106, and/or 108;202, 204, and/or 206), etc., associated with entities (e.g., firstentity, second entity, or other entity) and the DLDP 102, in accordancewith the defined data management criteria, as more fully describedherein. The DLDP 102 can apply the set of rules with regard to the DLDP102 and the systems, data stores, data, etc., associated with theentities to facilitate desirable management, access, and erasure of dataassociated therewith, in accordance with the set of rules.

The ingestion component 1106 also can monitor and track activity (e.g.,data-related activity) associated with systems, data stores, data, etc.,associated with entities. For instance, in connection with monitoringand tracking such activity, the ingestion component 1106 can receiveinformation (e.g., scanning results or other information) relating tothe scanning of systems, data stores (e.g., 104, 106, and/or 108; 202,204, and/or 206), data, etc., associated with the entities (e.g., firstentity, second entity, or other entity) that are associated with theDLDP 102. Such information can relate to or indicate data of users thathas been accessed in or retrieved from the systems or data storesassociated with entities, data of users that has been shared with thirdparty entities, and/or data of users that has been erased or deletedfrom the systems or data stores associated with entities.

The ingestion component 1106 can monitor and track activity associatedwith the secure data store 130. For example, in connection withmonitoring and tracking such activity, the ingestion component 1106 cantrack and receive information relating to accessing of data of usersstored in the secure data store 130, data of users retrieved from thesecure data store 130 that is shared with third party entities, and/ordata of users that is erased or deleted from the secure data store 130.

The ingestion component 1106 also can monitor and track informationrelating to DSR requests made by users, consents made by users withregard to data, or changes in consents made by users with regard todata. For example, in connection with monitoring and tracking suchinformation, the ingestion component 1106 can receive informationregarding DSR requests made by users, who those requesting users are,what data those users were requesting, what data those users were ableto gain access to, what system or data store (e.g., 104, 106, and/or108; 202, 204, and/or 206) of an entity (e.g., first entity, secondentity, or other entity) the data was retrieved from, the dates of therequests, and/or other desired information relating to DSR requests. Asanother example, the ingestion component 1106 can receive informationregarding consents or changes in consents, or refusals (e.g., denials)of consents, provided by users with regard to data of users or onlineactivity of users, such as consents, or refusals of consents, relatingto cookies or other tracking of user data or activity, consents relatingto receiving electronic communications (e.g., emails, text messages, orpop-up messages, etc.) from entities, or opt in or opt out consents.

The ingestion component 1106 further can monitor and track sharing ofdata with third party entities by the DLDP 102 or by systems, datastores, etc., associated with entities that can be monitored by the DLDP102. For instance, in connection with monitoring and tracking such data,the ingestion component 1106 can receive information relating to thesharing of data of user with third party entities by the DLDP 102 or bysystems, data stores (e.g., 104, 106, and/or 108; 202, 204, and/or 206),etc., associated with entities (e.g., first entity, second entity, orother entity) that can be monitored by the DLDP 102.

The governance component 404 can analyze the various information, whichcan be obtained as a result of the monitoring and tracking of activityand data associated with the DLDP 102 and the systems, data stores(e.g., 104, 106, and/or 108; 202, 204, and/or 206), data, etc.,associated with the entities (e.g., first entity, second entity, orother entity) that are associated with the DLDP 102. Based at least inpart on the results of analyzing such information, the governancecomponent 404 can determine whether the DLDP 102 and/or the systems,data stores, data, etc., associated with the entities are in compliancewith the set of rules, and correspondingly, applicable laws,regulations, or agreements, as more fully described herein. Thegovernance component 404 also can determine various risk scores (e.g.,relating to risk of not being in compliance) associated with variousparts of the DLDP 102 or associated entities and/or a privacy healthindex associated with a particular entity, based at least in part on theresults of analyzing such information and the set of rules, as morefully described herein. The governance component 404 further candetermine when anomalies (e.g., non-compliance issues) occur, based atleast in part on the results of analyzing such information and applyingthe set of rules, as more fully described herein. The governancecomponent 404 further can initiate, perform, or facilitate performingremediation actions to remedy or mitigate any detected anomalies, inaccordance with the defined data management criteria and applicablelaws, regulations, or agreements, as more fully described herein.

The governance component 404 can comprise a rules engine 1108 that candetermine the set of rules based at least in part on the various laws,regulations, and/or agreements. The rules engine 1108 can analyzerespective laws or regulations associated with respective jurisdictions,respective agreements associated with respective entities, and/orinformation relating thereto. Based at least in part on the results ofsuch analysis, the rules engine 1108 can determine respectiveobligations (e.g., legal obligations or requirements, or contractualobligations or requirements) relating to (e.g., deriving from, arisingout of, or necessitated by) the respective laws or regulationsassociated with the respective jurisdictions or the respectiveagreements associated with the respective entities. The rules engine1108 can determine respective rules of the set of rules for managing orgoverning data and communications of data associated with the DLDP 102and the associated systems, data stores (e.g., 104, 106, and/or 108;202, 204, and/or 206), etc., associated with the entities (e.g., firstentity, second entity, or other entity), based at least in part on therespective obligations, in accordance with the defined data managementcriteria.

For example, the various laws, regulations, and/or agreements cancomprise a first subset of laws or regulations associated with a firstsubset of jurisdictions and/or a first subset of agreements between afirst subset of entities, comprising the first entity, and a secondsubset of laws or regulations associated with a second subset ofjurisdictions and/or a second subset of agreements between a secondsubset of entities, comprising the second entity. Based at least in parton the results of analyzing the various laws, regulations, oragreements, including the first subset of laws or regulations, the firstsubset of agreements, the second subset of laws or regulations, and thesecond subset of agreements, the rules engine 1108 can determine a setof obligations comprising a first subset of obligations and a secondsubset of obligations. The first subset of obligations (e.g., firstsubset of legal or contractual obligations or requirements) can relateto (e.g., can derive from, arise out of, be necessitated by, and/orcorrespond to) the first subset of laws or regulations and/or the firstsubset of agreements. The second subset of obligations (e.g., secondsubset of legal or contractual obligations or requirements) can relateto the second subset of laws or regulations and/or the second subset ofagreements. Based at least in part on the set of obligations, comprisingthe first subset of obligations and the second subset of obligations,the rules engine 1108 can determine and generate the set of rules,comprising a first subset of rules and a second subset of rules. Thefirst subset of rules can correspond to, and facilitate enforcement of(e.g., by the DLDP 102 and/or the governance component 404) andcompliance with, the first subset of obligations, and accordingly, thefirst subset of laws or regulations and/or the first subset ofagreements. The second subset of rules can correspond to, and facilitateenforcement of (e.g., by the DLDP 102 and/or the governance component404) and compliance with, the second subset of obligations, andaccordingly, the second subset of laws or regulations and/or the secondsubset of agreements. The rules engine 1108 also can similarly determinea third subset of rules that can correspond to a third subset ofobligations based at least in part on the results of analyzing a thirdsubset of laws or regulations associated with a third jurisdictionand/or a third subset of agreements, and/or determine a fourth subset ofrules that can correspond to a fourth subset of obligations based atleast in part on the results of analyzing a fourth subset of laws orregulations associated with a fourth jurisdiction and/or a fourth subsetof agreements, and so on.

The laws, regulations, and/or agreements, and correspondingly the rules,can relate to the type of data, the privacy status or privacy type ofdata, DSRs of users with regard to their data, data subject rights ofusers, data access requests of users, data change requests of users,data protection requests of users, data erasure requests of users, theamount or type of data that can be collected, the users or entities thatare permitted to access data of users, the type of data that users orentities are permitted to access, sharing of data with third partyentities, the length of time that data associated with a user can beretained in a data store, the type or amount (e.g., number or frequency)of electronic communications (e.g., email messages, text messages, orphone calls) that are permitted to be sent to users, the amount of timewithin which to stop sending electronic communications after the userrequests to no longer receive electronic communications, security,authentication, or encryption protocols or algorithms that are to beused to secure stored data or to securely communicate data, noticesrelating to data or user rights that are to be provided to users, thedisposal (e.g., erasure or deletion of data), consents of users withregard to data, monitoring and enforcement relating to addressingprivacy complaints or compliance with laws, rules, or agreements, and/orother aspects relating to data protection. For example, a law,regulation, or agreement can specify or indicate the type(s) and/orprivacy type(s) of data regarding a user that an entity (e.g.,organization) is permitted to have access to, can specify or indicatewhat rights users have with regard to their data (e.g., data subjectrights), can specify or indicate how DSRs are to be processed, and/orcan specify or indicate an amount of time (e.g., 10 days (e.g., 10business or calendar days), 15 days, or 30 days) that an entity has tocomply with a request of a user to no longer receive a particular typeof electronic communication (e.g., email message, text message, or phonecall) from the entity.

The types of data can be or can comprise the types of personal dataelements, such as described herein. The privacy status or type of datacan comprise, for example, sensitive or personal data, protected data,non-sensitive data, or other desired type of privacy status or privacytype of data.

The rules generated by the rules engine 1108 can specify or indicateparticular actions or issues with regard to data are in non-compliancewith an applicable law, regulation, or agreement. The rules generated bythe rules engine 1108 also can comprise or relate to trends or trendspikes relating to data of users that is stored, accessed, tracked,communicated, or shared by an entity or platform. Certain rules also cancomprise a defined threshold value that can indicate whether a rule isbeing violated and/or whether a particular data or consent issue shouldbe checked into further to see if there is a problem to be addressed(e.g., remedied). For example, the governance component 404 can trackthe trends of users (e.g., customers) opting in to or opting out ofreceiving electronic communications from an entity, and can apply a rulethat can include a defined threshold value(s) to the trend datadetermined based at least in part on the tracking of such trends. Thedefined threshold value(s) can relate to an amount of difference betweenan average number of users opting in to receive electroniccommunications from the entity and a particular number of users optingin at a given time (e.g., a spike in users opting in at a given time),can relate to an amount of difference between an average number of usersopting out from receiving electronic communications from the entity anda particular number of users opting out at a given time (e.g., a spikein users opting out at a given time), can relate to a total number ofusers opting in at a given time, or can relate to a total number ofusers opting out at a given time. The governance component 404 cananalyze the trend data and apply the rule, including the definedthreshold value(s). Based at least in part on the results of theanalysis and applying of the rule, the governance component 404 candetermine whether a defined threshold value(s) has been satisfied (e.g.,breached or exceeded), which can indicate that there can be an anomaly(e.g., spike in the trend and/or possible non-compliance issue) withregard to opting in or opting out by users. If an anomaly is detected,the governance component 404 can provide information (e.g.,notification) to notify the entity of the anomaly and/or can facilitateremediating the anomaly, as more fully described herein.

The data management component 132, including the rights managementcomponent 402 and governance component 404, can utilize and apply (e.g.,enforce) the respective rules of the set of rules (e.g., first subset ofrules, second subset of rules, or other rules) with regard to the DLDP102 and respective systems, respective data stores (e.g., 104, 106,and/or 108; 202, 204, and/or 206), respective data of users, and/orrespective communications associated with users, etc., associated withrespective entities (e.g., first entity, second entity, or otherentity), to ensure or substantially ensure compliance, and/or tomitigate non-compliance, with the respective laws or regulations and/orrespective agreements associated with (e.g., respectively applicable to)the DLDP 102 and the respective systems, respective data stores,respective data of users, and/or respective communications associatedwith users, etc., associated with the respective entities.

The governance component 404 also can comprise a risk score component1110 (also referred to as risk assessment component herein) that candetermine (e.g., calculate) and generate risk scores (e.g., riskratings) that can indicate risk levels associated with the securing,storing, accessing, tracking, communicating, or sharing of data of usersby an entity or platform. KRI metrics can be or comprise the riskscores. KRIs can comprise leading indicators, current indicators, orlagging indicators. For instance, a leading KRI can relate to anemerging or potentially emerging risk trend regarding data protectionthat has some likelihood (e.g., a probability) of occurring in thefuture. A current KRI can relate to current data that can indicate alevel of risk regarding data protection. A lagging KRI can relate torisk-related events regarding data protection that occurred in the pastand have some likelihood of occurring again in the future.

The risk score component 1110 can determine or calculate a risk score ofa particular aspect (e.g., KRI metric, privacy principle, or platform)of or associated with an entity as a function of the impact of ananomaly (e.g., irregularity or non-compliance issue with regard to dataprotection) occurring and a likelihood of the anomaly occurring (e.g.,with regard to a particular KRI metric, privacy principle, or platform),in accordance with the defined data management criteria. The impact ofan anomaly can be or can relate to a consequence to the entity or userif the anomaly occurs. The likelihood of the anomaly occurring can be orcan relate to a probability that the anomaly will occur (e.g., willoccur at any time in the future, or will occur within a defined amountof time in the future). In some embodiments, the risk score component1110 can apply a rule-based approach, using the set of rules, tofacilitate determining (e.g., calculating) an impact (e.g., an amountand/or type of impact) that an anomaly can have on an entity or user. Incertain embodiments, the risk score component 1110 can apply alearning-based approach, using the artificial intelligence and/ormachine learning techniques and algorithms, such as described herein, tofacilitate determining (e.g., calculating) a likelihood (e.g., an amountof likelihood or probability) that an anomaly can have on an entity oruser.

In some embodiments, the risk score component 1110 can apply a riskscore matrix to facilitate determining risk scores associated with anentity. Referring to FIG. 12 (along with FIGS. 1, 2, 4, and 11), FIG. 12presents a diagram of an example risk score matrix system 1200 that canbe used to facilitate determining risk scores associated with an entity,in accordance with various aspects and embodiments of the disclosedsubject matter. The example risk score matrix system 1200 can comprise arisk score matrix 1202 that can be an n×n matrix that can present theimpact 1204 of an occurrence of an anomaly as a function of thelikelihood 1206 of the anomaly occurring, wherein n can be virtually anydesired number. In the example risk score matrix 1202, n can be 4,although a number less than or greater than 4 can be utilized. It is tobe appreciated and understood that, in other embodiments, if desired,the risk score matrix 1202 can be an n×m matrix or m×n matrix, wherein nand m can be virtually any desired numbers, and wherein n can bedifferent from (e.g., greater than or less than) m.

The risk score matrix 1202 can indicate an impact 1204 on an entity oruser of an occurrence of an anomaly, wherein, for example, the impact1204 can range from 1 (or less than 1) to 10, and wherein such numbercan be an integer or real number. The impact 1204 can range frommarginal impact 1208 to severe impact 1210 to critical impact 1212 tocatastrophic impact 1214 as the number of the impact 1204 increases from1 (or less than 1) to 10. For instance, on the lower end (e.g., 1 (orless than 1) up to 2.5) of the range of impact 1204, the impact 1204 canbe marginal 1208, which can indicate that there may be a marginal impact(e.g., a marginal amount of negative impact) to an entity or user if theparticular type of anomaly occurs, but relatively speaking, the amountof impact to the entity or user if the anomaly were to occur isrelatively low or minimal. In the lower-middle part (e.g., 2.51 up to5.00) of the range of impact 1204, the impact 1204 can be severe 1210,which can indicate that there may be a more significant or severe impact(e.g., severe negative impact) to an entity or user if the particulartype of anomaly occurs, but relatively speaking, the amount of impact ofthe anomaly to the entity or user still can be manageable and/oraddressable (e.g., can be mitigated, remedied, absorbable) if theanomaly occurs. In the upper-middle part (e.g., 5.01 up to 7.50) of therange of impact 1204, the impact 1204 can be critical 1212, which canindicate that there can or may be a critical, harmful, or unacceptableimpact (e.g., critical or unacceptably high negative impact) to anentity or user if the particular type of anomaly occurs, wherein theamount of impact to the entity or user still may possibly be manageable,however, the consequences of such an anomaly are undesirably (e.g.,unacceptably) high, it can be desirable to address (e.g., can bemitigate or remedy) such an impact if it were to occur, although it canbe more difficult or problematic to address such an impact if it were tooccur. In the upper part (e.g., 7.51 up to 10.00) of the range of impact1204, the impact 1204 can be catastrophic 1214, which can indicate thatsuch an impact to an entity or user if the particular type of anomalyoccurs would be catastrophic to the entity or user, likely would not bemanageable, and likely would not be able to be desirably remedied,mitigated, or corrected if such an impact were to occur.

With regard to the likelihood 1206 of an anomaly occurring, the riskscore matrix 1202 can indicate relative ranges of likelihood (e.g.,probability) that a particular anomaly will occur (e.g., at any time inthe future, or within a defined amount of time in the future). Forinstance, on the lower end of the range of likelihood 1206, thelikelihood 1206 can be improbable 1216, which can indicate that there isa relatively (e.g., very) low likelihood that a particular type ofanomaly will occur. For example, a likelihood in the improbable range1216 can indicate that there is less than a 1% probability (or otherdesirably low probability, such as, e.g., 5% probability or less) thatthe particular type of anomaly will occur. In the lower-middle part ofthe range of likelihood 1206, the likelihood 1206 can be remote 1218,which can indicate that the likelihood that a particular anomaly willoccur can still be relatively low (e.g., probability of less than 50%),but such likelihood is higher than that of the improbable range 1216. Inthe upper-middle part of the range of likelihood 1206, the likelihood1206 can be probable 1220, which can indicate that there can be arelatively high likelihood (e.g., greater than 50% probability, but lessthan 75% probability) that a particular type of anomaly will occur. Inthe upper part of the range of likelihood 1206, the likelihood 1206 canbe frequent 1222, which can indicate that a particular type of anomalycan frequently occur and/or there can be a high probability (e.g.,greater than 75% probability) that the particular type of anomaly willoccur.

As can be observed in FIG. 12, the example risk score matrix 1202includes some example risk scores that can be associated with an exampletype of anomaly. The example risk scores can range from 1 to 100, forexample. A risk rating 1224 (e.g., risk score) can indicate an amount ordegree of risk that an anomaly may occur and an associated risk level1226 that can indicate what particular level of risk is associated witha particular risk rating. For instance, the risk rating 1224 can rangefrom 1 up to a maximum score of 100, where 100 can indicate the most(e.g., worst) risk and 1 can indicate the lowest level of risk. A riskrating range of 1 through 25 (1228) can be associated with a low risklevel 1230, a risk rating range of 26 through 50 (1232) can beassociated with a medium risk level 1234, a risk rating range of 51through 75 (1236) can be associated with a serious risk level 1238, anda risk rating range of 76 through 100 (1240) can be associated with ahigh risk level 1242.

With further regard to the example risk scores in the example risk scorematrix 1202, as can be observed in FIG. 12, an anomaly, which isdetermined to have a marginal impact 1208 on an entity or user and alikelihood of improbable 1216, can have a low risk score (e.g., a riskscore of 10 (1244) or other low risk score that ranges from 1 to 25) inthe low risk range 1230. On the other end of the spectrum, an anomaly,which is determined to have a catastrophic impact 1214 on an entity oruser and a likelihood of frequent 1222, can have a high risk score(e.g., a risk score of 100 (1246) or other high risk score that is 76 upto 100) in the high risk range 1242. For example, a risk score of 100can indicate that the impact 1204 of the anomaly on an entity or usercan be 10, and the likelihood 1206 of the anomaly occurring can be 10.As also can be observed in the example risk score matrix 1202, asindicated at reference numeral 1248, an anomaly, which is determined tohave a marginal impact 1208 on an entity or user, can still pose amedium risk 1234, for example, if the likelihood 1206 of such anomalyoccurring is probable 1220 or frequent 1222. Generally, as the amount ofimpact 1204 of an occurrence of an anomaly to an entity or userincreases in relation to a particular likelihood, the risk score canincrease (and vice versa), and, as the likelihood 1206 of such anomalyoccurring increases in relation to a particular impact level, the riskscore can increase (and vice versa).

It is to be appreciated and understood that the example risk scorematrix system 1200 is but one type of risk score approach that the riskscore component 1110 can use to determine risk scores. In accordancewith various other embodiments, the risk score component 1110 canutilize virtually any other desired technique, algorithm, approach,calculations, or determinations to determine risk scores, determine animpact of an anomaly if it occurs, or determine a likelihood of ananomaly occurring.

Turning briefly to FIG. 13 (along with FIGS. 1, 2, 4, and 11), FIG. 13presents a diagram of example sources 1300 that can be accessed toobtain data that can be used to determine (e.g., derive or calculate)KRIs, in accordance with various aspects and embodiments of thedisclosed subject matter. With regard to, and to facilitate evaluatingKRIs relating to, data subject rights 1302, the example sources 1300 caninclude customer data 1304 (e.g., user data) and privacy enhancingtechnology (PET) and Compass application 1306. For instance, thegovernance component 404 can obtain information relating to data subjectrights 1302 through the customer data 1304, which can be obtained fromthe customers directly or indirectly from another source, from thesecure data store 130, from a data store (e.g., 104, 106, or 108; or202, 204, or 206), or from another desired source.

The governance component 404 also can obtain information relating todata subject rights 1302 through the PET and/or Compass application1306. In accordance with various embodiments, the DLDP 102, datamanagement component 132, or governance component 404 can comprise,utilize, or access PETs, the Compass application, or another desireddata security or protection technology or application to facilitateperforming various aspects of the disclosed subject matter, such asdescribed herein. The DLDP 102, data management component 132, and/orgovernance component 404 can utilize PETs to facilitate desirablycollecting, processing, storing, sharing, or utilizing data of users, inaccordance with the set of rules and corresponding laws, regulations,and/or agreements, in accordance with the defined data managementcriteria. PETs can comprise technologies and/or components (e.g.,modules) that can be used to facilitate protecting data of users,ensuring that users can have information that can be suitable to enablea user to give an informed consent with regard to the collecting,processing, storing, sharing, or utilization of their data. PETs alsocan be utilized to facilitate (e.g., enable) users to exercise theirrights (e.g., data subject rights) with regard to data. The Compassapplication or other data security or protection application can beutilized to facilitate (e.g., enable) desirable managing of dataprotection of data of users. The governance component 404 can access orobtain information utilized or generated by the PET and/or Compassapplication 1306 (or other desired technology or application) withregard to data subject rights 1302 of users.

With regard to, and to facilitate evaluating KRIs relating to, sharingor oversharing of data with third parties 1308 (oversharing with TPs),the governance component 404 can obtain information from or relating toinformation security assessments 1310 (infosec assessments), informationfrom or relating to sharing personal attributes 1312, and/or informationfrom or relating to information risk assessment (IRA), privacy riskassessment (PRA), data protection impact assessment (DPIA), or othertypes of risk or impact assessments 1314. For instance, the governancecomponent 404 can obtain information from or relating to informationsecurity assessments 1310 that can be performed by the governancecomponent 404 or another desired service, such as, for example, ServiceNow or another desired security service. The governance component 404also can obtain information from or relating to sharing personalattributes 1312, for example, by parsing such information regardingsharing personal attributes from APIs, UC4, control-m logs, or anotherdesired data transfer or management component or application. Thegovernance component 404 also can obtain information from or relating toIRA, PRA, DPIA, or other types of risk or impact assessments 1314, forexample, from Hiperos or another desired risk management component,application, or provider (e.g., another desired third-party riskmanagement component, application, or provider).

With regard to, and to facilitate evaluating KRIs relating to, scancoverage 1316 (oversharing with TPs), the governance component 404 canobtain information relating to scan coverage 1316 from the SPDR 1318(e.g., scanner component(s) 124, 208, or 210), universal databaseconnector (UDC) 1320, scan repository 1322 (e.g., data store 302 or datastore 304 of FIG. 3), and/or metadata resources 1324 of or associatedwith an entity (e.g., organization). The information relating to scancoverage 1316 can indicate what data stores or databases of an entityhave been scanned (e.g., have been scanned during a defined timeperiod), what information (e.g., what types of data and their respectivedata privacy statuses) has been scanned, what data stores or databaseshave not been scanned (e.g., have not been scanned during the definedtime period), and/or other desired information relating to scan coverage1316. A UDC 1320 can be associated with a scanner component (e.g.,scanner component 124, 208, or 210), and can facilitate desirablyconnecting to (e.g., efficiently and/or directly connecting to) a datastore (e.g., 104, 106, or 108; 202, 204, or 206) to facilitate desirablescanning of data from the data store and/or indexing of the scanneddata.

With regard to, and to facilitate evaluating KRIs relating to, marketingnotifications 1326, the governance component 404 can obtain informationrelating to marketing notifications 1326 from a variety of data sources,such as, for example, unified notification platform (UNP)—explicitpreferences 1328, UNICA campaign and response 1330, customer consentimplicit preference 1332, and customer data 1334. For example, thegovernance component 404 can receive data relating to preferences (e.g.,explicit preferences) of customers with regard to marketingnotifications 1326 from the UNP 1328 (or another desired notificationplatform). As another example, the governance component 404 also canreceive data relating to marketing notifications 1326 from the UNICAcampaign and response 1330 (or another desired marketing campaigntechnology, application, or platform).

Referring to FIG. 14 (along with FIGS. 1, 2, 4, and 11), FIG. 14 depictsa block diagram of an example risk score and privacy health indexprocess flow 1400 that can be used to facilitate determining risk scoresand a privacy health index associated with an entity, in accordance withvarious aspects and embodiments of the disclosed subject matter. Thegovernance component 404 can determine various risk scores and a privacyhealth index for any desired entity that is associated with the DLDP102, data management component 132, and/or governance component 404. Forexample, the entity can be an entity that is operating, owning, and/ormanaging the DLDP 102, data management component 132, governancecomponent 404, and/or one or more data stores associated with (e.g.,communicatively connected to) the DLDP 102 and/or governance component404. As another example, an entity can operate, own, and/or manage a setof data stores located in one or more jurisdictions, wherein the set ofdata stores can be monitored, scanned, tracked, and/or evaluated (e.g.,evaluated for compliance with applicable laws, regulations, oragreements) by the DLDP 102, data management component 132, and/orgovernance component 404.

In accordance with the example risk score and privacy health indexprocess flow 1400, the governance component 404 (e.g., the risk scorecomponent 1110 or other component of the governance component 404) candetermine various KRIs, which can be or can comprise risk scores,relating to various risk factors relating to data protection. The riskfactors, in part, can relate to risks associated with non-compliancewith applicable laws, regulations, or agreements or other anomalies(e.g., irregularities) relating to data protection. The KRIs or riskscores can comprise, for example risk scores (KRIs) 1402, 1404, 1406,1408, 1410, 1412, and/or 1414 relating to various and respective riskfactors, which can be relevant to respective privacy principles.

The privacy principles can comprise, for example, security for privacy1416, quality 1418, collection 1420, use, retain and dispose 1422,management 1424, access 1426, disclosures to third parties 1428, choiceand consents 1430, notice 1432, and/or another desired privacyprinciple. Security for privacy 1416 can relate to or involve securityfor privacy of data of users, such as, for example, securing orprotecting data from data breaches. Quality 1418 can involve, forexample, quality relating to personal data detection accuracy or otherdesired quality issues or factors relating to data protection.Collection 1420 can relate to, for example, the collection of datausers. Use, retain and dispose 1422 can relate to, for example, the use,retention, or disposition of data of users, scanning coverage of thescanning of data of or associated with users, or other desired factors.Management 1424 can involve management of data processing of data ofusers, including, for example, PIAs, data protection impact assessments(DPIAs), or another desired type of impact or risk assessment. Access1426 can relate to access of data of users by other users or otherentities, data subject requests associated with users, or other dataaccess related issues or factors. Disclosures to third parties 1428 canrelate to disclosure of data of users to third party entities, privacycomplaints (e.g., privacy complaint from a regulator or user) regardingdisclosure of data of users, PIAs relating to disclosure of user data tothird party entities, or another issue or factor associated withdisclosures to third parties. Choice and consents 1430 can relate to,for example, choices and consents of users with regard to collection andprocessing of their data, cookies, electronic communications to users,or another issue or factor associated with choices or consents of users.Notice 1432 can relate to notices (e.g., data privacy statement ornotice) or transparency issues relating to data collection andprocessing of data of users, electronic communications to users, orother notice related issues or factors.

A particular risk score (e.g., risk score 1402) and associated riskfactor can relate to or apply to one or more privacy principles (e.g.,1416, 1418, 1420, 1422, 1424, 1426, 1428, 1430, and/or 1432). Forexample, a particular risk score and associated risk factor can relateor apply to only a single privacy principle or a particular risk scoreand associated risk factor can relate or apply to two or more privacyprinciples. Also, two or more risk scores or associated risk factors canrelate to or apply to a particular privacy principle.

In some embodiments, the risk score component 1110 can apply respectiveweights (e.g., weight values) to respective risk scores (or respectiveKRI metrics) to generate respective weighted risk scores (or weightedKRI metrics). For instance, the risk score component 1110 can determinerespective weights to apply to respective risk scores based at least inpart on the respective significance of the respective risk scores orassociated risk factors to a privacy principle(s), in accordance withthe defined data management criteria. The risk score component 1110 canapply the applicable weight (e.g., weight value) to a particular riskscore to generate the weighted risk score. For example, the weight canbe a value that is less than 1.00, equal to 1.00, or more than 1.00, andthe risk score component 1110 can determine (e.g., calculate) theweighted risk score as a function of the risk score and the weight(e.g., weighted risk score=risk score×weight value). The weight to beapplied to a particular risk score can be the same with regard to eachprivacy principle with which the particular risk score is going to beused, or the weight to be applied to a particular risk score can bedetermined based at least in part on the privacy principle with which itis going to be used and/or the risk factor associated with theparticular risk score, as indicated or specified by the defined datamanagement criteria.

In certain embodiments, with regard to each privacy principle (e.g.,1416, 1418, 1420, 1422, 1424, 1426, 1428, 1430, or 1432), the risk scorecomponent 1110 can determine a risk score of or associated with theprivacy principle as a function of the weighted risk scores that areapplicable to that privacy principle. For example, the risk scorecomponent 1110 can determine (e.g., calculate) a risk score of orassociated with a privacy principle as a function of an average of theweighted risk scores that are applicable to that privacy principle. Inother embodiments, the risk score component 1110 can determine a riskscore of or associated with a privacy principle as or based at least inpart on a median value of the weighted risk scores that are applicableto that privacy principle, a trimmed average or mean of such weightedrisk scores, a normalized risk score derived from the applicableweighted risk scores, or a peak weighted risk score of all theapplicable weighted risk scores, as indicated or specified by thedefined data management criteria.

If and as desired, the risk score component 1110 also can determinerespective risk scores of or associated with the respective platformsbased at least in part on (e.g., as a function of) the respective riskscores of the respective privacy principles, as applicable to aparticular platform. The platforms can comprise, for example, the datadiscovery platform 1434 (e.g., DLDP 102), the data subject rightsplatform 1436, the third party management platform 1438, the notice andconsents platform 1440, and/or another desired platform of or associatedwith the DLDP 102 (e.g., the governance platform, or the rightsmanagement platform, etc.). In some embodiments, privacy principles,such as security for privacy 1416, quality 1418, collection 1420, use,retain and dispose 1422, management 1424, and/or another desired privacyprinciple can be associated with (e.g., relevant or applicable to) thedata discovery platform 1434. Privacy principles, such as access 1426and/or another desired privacy principle can be associated with the datasubject rights platform 1436. Privacy principles, such as disclosures tothird parties 1428 and/or another desired privacy principle can beassociated with the third party management platform 1438. Privacyprinciples, such as choices and consents 1430, notice 1432, and/oranother desired privacy principle can be associated with the notice andconsents platform 1440.

The risk score component 1110 can apply respective weights (e.g., weightvalues) to respective risk scores associated with the respective privacyprinciples to generate respective weighted risk scores. For example, therisk score component 1110 can determine respective weights to apply torespective risk scores associated with the respective privacy principlesbased at least in part on the respective significance of the respectiverisk scores and associated privacy principles to the particular platform(e.g., 1434, 1436, 1438, or 1440, etc.), in accordance with the defineddata management criteria. The risk score component 1110 can apply theapplicable weight (e.g., weight value) to a particular risk score togenerate the weighted risk score, wherein the weight value can be lessthan 1.00, equal to 1.00, or more than 1.00, and wherein the risk scorecomponent 1110 can determine the weighted risk score as a function ofthe risk score and the weight (e.g., weighted risk score=riskscore×weight value). The weight to be applied to a particular risk scorecan be the same with regard to each platform with which the particularrisk score is going to be used, or the weight to be applied to aparticular risk score can be determined based at least in part on theplatform with which it is going to be used and/or the privacy principleassociated with the particular risk score, as indicated or specified bythe defined data management criteria.

In certain embodiments, with regard to each platform (e.g., 1434, 1436,1438, or 1440, etc.), the risk score component 1110 can determine a riskscore of or associated with the platform as a function of the weightedrisk scores that are applicable to that platform. For example, the riskscore component 1110 can determine (e.g., calculate) a risk score of orassociated with a platform (e.g., 1434, 1436, 1438, or 1440, etc.) as afunction of an average of the weighted risk scores that are applicableto that privacy principle. In other embodiments, the risk scorecomponent 1110 can determine a risk score of or associated with aparticular platform as or based at least in part on a median value ofthe weighted risk scores that are applicable to that platform, a trimmedaverage or mean of such weighted risk scores, a normalized risk scorederived from such weighted risk scores, or a peak weighted risk score ofall the applicable weighted risk scores, as indicated or specified bythe defined data management criteria.

For example, the risk score component 1110 can determine a risk score ofor associated with the data discovery platform 1434 as a function of(e.g., as an average of) the respective weighted risk scores of securityfor privacy 1416, quality 1418, collection 1420, use, retain and dispose1422, management 1424, and/or another applicable privacy principle. Therisk score component 1110 can determine a risk score of or associatedwith the data subject rights platform 1436 as a function of (e.g., as anaverage of) the respective weighted risk scores of the access 1426and/or another applicable privacy principle (if access 1426 is the onlyapplicable privacy principle, the weight value for that privacyprinciple can be 1.00 or there may be no weight value used). The riskscore component 1110 can determine a risk score of or associated withthe third party management platform 1438 as a function of (e.g., as anaverage of) the respective weighted risk scores of the disclosures tothird parties 1428 and/or another applicable privacy principle (ifdisclosures to third parties 1428 is the only applicable privacyprinciple, the weight value for that privacy principle can be 1.00 orthere may be no weight value used). The risk score component 1110 candetermine a risk score of or associated with the notice and consentsplatform 1440 as a function of (e.g., as an average of) the respectiveweighted risk scores of choice and consents 1430, notice 1432, and/oranother applicable privacy principle.

In some embodiments, the risk score component 1110 can determine anoverall risk score associated with an entity or the system (e.g., riskscore 1442 by platforms and privacy principles) based at least in parton the respective risk scores of the respective platforms (e.g., 1434,1436, 1438, or 1440, etc.). For instance, the risk score component 1110can determine respective weights for the respective platforms (e.g.,1434, 1436, 1438, or 1440, etc.) and can apply the respective weights tothe respective risk scores associated with the respective platforms togenerate respective weighted risk scores. For example, the risk scorecomponent 1110 can determine respective weights to apply to respectiverisk scores associated with the respective platforms based at least inpart on the respective significance of the respective risk scores andassociated platforms, in accordance with the defined data managementcriteria. In some embodiments, the risk score component 1110 candetermine (e.g., calculate) a risk score 1442 (e.g., overall risk score)by platforms and privacy principles as a function of an average of therespective weighted risk scores of the respective platforms (e.g., 1434,1436, 1438, or 1440, etc.). In other embodiments, the risk scorecomponent 1110 can determine the risk score 1442 by platforms andprivacy principles as or based at least in part on a median value of therespective weighted risk scores of the respective platforms, a trimmedaverage or mean of such weighted risk scores, a normalized risk scorederived from such weighted risk scores, or a peak weighted risk score ofsuch weighted risk scores, as indicated or specified by the defined datamanagement criteria.

The governance component 404 also can comprise a privacy health indexcomponent 1112 that can determine a privacy health index 1444 associatedwith an entity (e.g., organization) or the system based at least in parton the risk score 1442 by platforms and privacy principles, riskcontrols 1446, remediations 1448, exceptions 1450, and/or anotherdesired factor, in accordance with the defined data management criteria.Risk controls 1446 can relate to regulatory and operational riskcontrols (e.g., risk policies, procedures, protocols, technologies,processes, techniques, or devices, etc.) that can facilitate (e.g.,enable) managing, reducing, or modifying risks with regard to dataprotection, and facilitate desirable compliance with applicable laws,regulations, and agreements with regard to data protection. The privacyhealth index component 1112 can quantify (e.g., determine or measure)the risk controls 1446 to generate a risk control score that canrepresent or indicate the relative level, status, or effectiveness ofthe risk controls 1446. Remediations 1448 can relate to remediationactions, policies, procedures, protocols, technologies, processes,techniques, or devices, etc., that have or can be implemented toremediate, mitigate, or rectify any non-compliance issues or otheranomalies in connection with data protection. The privacy health indexcomponent 1112 can quantify the remediations 1448 to generate aremediation score that can represent or indicate the relative level,status, or effectiveness of the remediations 1448. Exceptions 1450 canrelate to exceptions actions, notifications, policies, procedures,protocols, technologies, processes, techniques, or devices, etc., thatcan be used to identify and provide notifications regarding anynon-compliance issues or other anomalies in connection with dataprotection to facilitate notifying an entity (e.g., entityrepresentative) of a non-compliance issue or other anomaly and/orremediating a non-compliance issue or other anomaly. The privacy healthindex component 1112 can quantify the exceptions 1450 to generate anexceptions score that can represent or indicate the relative level,status, or effectiveness of the exceptions 1450. The privacy healthindex component 1112 can determine (e.g., calculate) the privacy healthindex 1444 as a function of (e.g., combination of, sum of, or averageof, etc.) the risk score 1442, the quantifiable value (e.g., riskcontrol score) of the risk controls 1446, the quantifiable value (e.g.,remediation score) of the remediations 1448, and the quantifiable value(e.g., exceptions score) of the exceptions 1450, in accordance with thedefined data management criteria.

The governance component 404 can comprise a validation component 1114(e.g., validation engine) that can monitor or track the collecting,processing, accessing, storing, sharing, or utilization of data ofusers, trends relating thereto, information (e.g., IRAs, PRAs, DPIAs, orother assessments, etc.) relating thereto, the set of rules (e.g., thefirst subset of rules associated with the first jurisdiction, or thesecond subset of rules associated with the second jurisdiction, etc.),DSRs, etc. The validation component 1114 can analyze the data,information, trends, rules, and/or DSRs, etc. Based at least in part onthe results of such analysis, the validation component 1114 can validateor verify the compliance of the DLDP 102, its constituent or associatedplatforms (e.g., rights management component 402, or governancecomponent 404, etc.), data stores (e.g., 104, 106, and/or 108; and/or202, 204, and/or 206; etc.) associated with entities with the respectiverules of the set of rules (and corresponding laws, regulations, and/oragreements), validate or verify the extent of such compliance, and/ordetermine or identify non-compliance with the set of rules or otheranomalies associated with the data, information, trends, and/or DSRs,etc.

For instance, with regard to a first entity that owns, operates, ormanages the DLDP 102, its constituent or associated platforms, and thefirst set of data stores 104, 106, and 108, the validation component1114 can validate or verify that the first entity, including theassociated DLDP 102, its constituent or associated platforms, and thefirst set of data stores 104, 106, and 108 are in compliance with thefirst subset of rules (and corresponding first set of laws andregulations associated with the first jurisdiction and/or firstagreement), validate or verify the extent of such compliance, and/ordetermine or identify (e.g., detect and identify) non-compliance withthe first subset of rules or other anomalies associated with the data,information, trends, and/or DSRs, etc., of or associated with firstentity.

With regard to a second entity that owns, operates, or manages thesecond set of data stores 202, 204, and 206, the validation component1114 can validate or verify that the second entity, including the secondset of data stores 202, 204, and 206 (and to the extent applicable, theassociated DLDP 102 and its constituent or associated platforms) are incompliance with the second subset of rules (and corresponding second setof laws and regulations associated with the second jurisdiction and/orsecond agreement), validate or verify the extent of such compliance,and/or determine or identify non-compliance with the second subset ofrules or other anomalies associated with the data, information, trends,and/or DSRs, etc., of or associated with second entity.

If the validation component 1114 detects an anomaly (e.g., anon-compliance issue or other anomaly), the validation component 1114can present anomaly information that can indicate or specify that theanomaly has been detected, the type of anomaly, the entity, platform,and/or data store associated with the anomaly, the date(s)/time(s) ofthe occurrence(s) the anomaly, the date(s)/time(s) that the anomaly wasdetected, and/or other desired information relating to the anomaly.

In some embodiments, the governance component 404 can be associated with(e.g., communicatively connected to) an application component 1116(e.g., front end application) that can access certain informationregarding the DLDP 102, its constituent or associated platforms, and/ordata stores associated with entities, in accordance with access rightsgranted to users (e.g., by the rights management component 402). Theapplication component 1116 can be implemented or utilized by acommunication device, such as, for example, communication device 138 ofFIG. 1.

For example, an authorized user (e.g., associated with the first entity)can utilize the application component 1116 and/or communication device138 to access certain information regarding the DLDP 102, itsconstituent or associated platforms, and/or the first set of data stores104, 106, and/or 108 associated with the first entity, in accordancewith access rights granted to such user, wherein such certaininformation can comprise status or snapshot information regarding theoperation of the DLDP 102, its constituent or associated platforms,and/or the first set of data stores, data discovery or scanning results(e.g., real-time scan results or previously performed scanning results)associated with the first set of data stores, risk scores associatedwith the privacy principles, the DLDP 102, its constituent or associatedplatforms, and/or the first set of data stores, a privacy health index(e.g., privacy health index 1444) associated with the first entity,and/or compliance, non-compliance, and/or anomaly information relatingto the DLDP 102, its constituent or associated platforms, and/or thefirst set of data stores, etc. The data management component 132,including the governance component 404, can present or facilitatepresenting such certain information to the application component 1116and/or communication device 138 for viewing by the authorized user.

With regard to the second entity and associated second set of datastores 202, 204, and/or 206, if an authorized user (e.g., the authorizeduser associated with the first entity or another authorized userassociated with the second entity) has certain access rights to accesscertain information (e.g., status or snapshot information; risk scores;privacy health index; and/or compliance, non-compliance, and/or anomalyinformation; etc.) relating to the second set of data stores 202, 204,and/or 206 associated with the second entity, the authorized user canutilize the application component 1116 and/or communication device 138to access such certain information relating to second set of data storesassociated with the second entity. Such certain information can compriseinformation stored in the DLDP 102 (e.g., secure data store 130 of theDLDP 102), its constituent or associated platforms (e.g., rightsmanagement component 402, or governance component 404, etc.) thatrelates to the second set of data stores and/or information obtainedfrom scanning (e.g., real-time scanning or previously performedscanning) the second set of data stores (e.g., scanning results storedin the scanner component 210).

Depending in part on the type and/or severity of an anomaly, it can ormay be desirable (e.g., wanted, appropriate, necessary, or required) toprovide a notification regarding the anomaly, and/or to perform aremediation action to remedy, correct, or mitigate the anomaly, forexample, when doing so is in accordance with the set of rules,corresponding laws, regulations, or agreements, and the correspondingdefined data management criteria. In that regard, the governancecomponent 404 can comprise a remediation component 1118 and notificationcomponent 1120 (e.g., notification engine) that can facilitateaddressing non-compliance issues or other anomalies. For instance, inresponse to detecting an anomaly (e.g., non-compliance issue or otheranomaly) for which notification and/or remediation can be desirable, thevalidation component 1114 can initiate a remediation with theremediation component 1118 and initiate a notification with thenotification component 1120 to facilitate addressing the anomaly, asmore fully described herein.

The notification component 1120 can generate and provide (e.g.,communicate) notification or alert messages relating to operation of theDLDP 102, its constituent or associated platforms, the first set of datastores 104, 106, and/or 108, and/or second set of data stores 202, 204,and/or 206, including notification or alert messages regarding ananomaly (e.g., non-compliance issue or other anomaly) detected by thegovernance component 404. For example, in response to the validationcomponent 1114 detecting an anomaly (e.g., a privacy breach with regardto data of users; a breach of a condition with regard to sendingelectronic communications to a user; a breach with regard to a consentissue involving a user(s); or a breach of a condition or threshold levelrelating to data of users; etc.), the validation component 1114 canpresent the anomaly information to the notification component 1120. Thenotification component 1120 can generate a notification message that cancomprise the anomaly information. In some embodiments, the notificationcomponent 1120 can communicate the notification message to a user (e.g.,an entity representative who can handle data privacy breaches oranomalies), for example, via a communication device, such ascommunication device 138, to notify the user regarding the anomaly. Thenotification message can be or can comprise an exception or alert ticketrelating to the anomaly. The notification message also can request thatthe anomaly issue be reviewed to determine whether the anomaly is validand/or determine whether a remediation action is to be performed toremedy, correct, or mitigate the anomaly.

Referring briefly to FIG. 15 (along with FIGS. 1, 2, 4, and 11), FIG. 15presents a diagram of an example exception message 1500 (e.g., exceptionor alert ticket message) relating to an example anomaly issue relatingto data subject requests, in accordance with various aspects andembodiments of the disclosed subject matter. The example exceptionmessage 1500 can comprise an issue description 1502 that can describethe anomaly issue that was detected. For instance, in the exampleexception message 1500, the issue description 1502 indicates that thePrivacy Platform (e.g., governance platform) identified a data subjectrequest(s) that exceeded the completion deadline of 30 days. The exampleexception message 1500 also can include a detected time 1504 that canindicate the time that the anomaly was detected and/or the alert of theanomaly was generated.

The example exception message 1500 also can comprise details 1506regarding the anomaly. The details 1506 can comprise various attributes1508 that can indicate and/or provide information regarding the anomaly.In the example exception message 1500 regarding the anomaly involvingdata subject requests exceeding the completion deadline, the attributes1508 can comprise, for example, data subject request number, category ofrequest, status of ticket (e.g., exception ticket), customer country,ticket creation date, ticket resolution date, and/or the days exceededfor ticket completion. In some embodiments, the example exceptionmessage 1500 can indicate that there is an attachment 1510 that can bereferenced to obtain additional or more specific information (e.g.,additional details) regarding the anomaly.

The example exception message 1500 further can comprise a call to action1512 that can request that the message recipient take appropriate action(e.g., remediation action) to determine validity of the anomaly andremediate or resolve the anomaly issue. For example, the call to action1512 can request that the message recipient review the alert (e.g.,exception message 1500 and/or attached information) for validity andresolve the exception ticket and/or anomaly accordingly, and, in casethe alert can be ignored (e.g., due to there being no actual problem,such as no actual non-compliance issue that has to be remedied orcorrected), send a message (e.g., email message) with the reason thatthe exception ticket can be ignored. For instance, the call to action1512 can request that the anomaly issue be reviewed by a user (e.g.,entity representative) to determine whether the anomaly is valid and/ordetermine whether a remediation action is to be performed to remedy,correct, or mitigate the anomaly; and, if a remediation action is to beperformed, perform the remediation action and report back that theremediation action has been performed and the anomaly issue has beenresolved or otherwise remediated; and, if the anomaly is determined tonot be valid (e.g., is not an issue that has to be remediated), reportthat the anomaly is determined to not be valid or otherwise does nothave to be addressed.

The example exception message 1500 also can include a privacy impactstatement 1514 that can include information (e.g., privacyimpact-related information) that can indicate legal and/or contractualinformation relating to the anomaly issue. For example, with regard toan anomaly involving data subject requests not being completed in atimely manner, the privacy impact statement 1514 can provide informationrelating to an applicable privacy law and/or agreement (e.g., SLA)regarding data subject requests, and/or information relating to theimpact or potential impact of failing to comply with the applicableprivacy law and/or agreement.

In some embodiments, the notification component 1120 also cancommunicate an exception message (e.g., a different type of notificationmessage) to an exception component 1122, which can be part of the backend 1104 of the governance component 404. The exception message cancomprise same or similar information, or additional information,regarding the anomaly that was contained in the notification messagesent to the user. The exception component 1122 (e.g., exception engine)can analyze and process the exception message. Based at least in part onthe results of the analysis and processing, the exception component 1122can document the exception incident (e.g., the anomaly) and can presentor make available information (e.g., anomaly information) relating tothe exception incident, so that a user (e.g., entity representative) canaddress (e.g., check out, remediate, or take other appropriate actionwith regard to) the anomaly. For example, if the anomaly relates tocustomers, who opted out of receiving marketing emails from the entity,continuing to receive marketing emails from the entity, the exceptioncomponent 1122 can present or make available, to the user, informationrelating to this anomaly of improperly sending marketing emails tocustomers who opted out of receiving such emails. As another example, ifthe anomaly relates to data subject requests that being completed withinthe applicable deadline, the exception component 1122 can present ormake available, to the user, information relating to the anomaly of datasubject requests not being completed by the applicable deadline.

In some embodiments, the exception component 1122 can be associated with(e.g., communicatively connected to) or can comprise core platforms 1124that can facilitate analyzing and processing exception tickets regardinganomalies, working in conjunction with appropriate users to handle oraddress the exception tickets (e.g., working in conjunction with amarketing representative or a software engineer or programmer regardinga problem relating to improperly sending of marketing emails tocustomers; working in conjunction with a representative of the secondentity regarding a privacy breach of data of users involving the secondset of data stores 202, 204, and/or 206; or working in conjunction withan entity representative, who handles issues relating to data subjectrequests, that there are data subject requests that are not beingprocessed and completed within the applicable time limit), performing orfacilitating performing remediation actions, and/or reporting results ofvalidation of an anomaly issue or remediation of an anomaly issue. Thecore platforms 1124 can comprise or employ resources, devices, userinterfaces, servers, file systems, applications, technologies,processes, procedures, and protocols that can facilitate performing thevarious operations or actions, such as described herein, to desirablyaddress exception tickets and resolve anomaly issues.

The remediation component 1118 can monitor and track the progress of theremediation or exception validation being performed by the exceptioncomponent 1122, core platforms 1124, and/or user(s) that are addressingthe anomaly issue. If the remediation component 1118 determines that theanomaly issue is not being suitably or timely addressed by the user, theremediation component 1118 or notification component 1120 can send out areminder message or other suitable message to a communication device ormessaging account (e.g., email account, or text messaging account) ofthe user to notify or remind the user that the anomaly issue still hasnot been addressed.

In response to being notified of the anomaly issue, the user or anotheruser can check out the anomaly issue to determine whether it is valid,and, if so, can perform a remediation action to resolve or remediate theanomaly issue. For example, with regard to the improper sending ofmarketing emails to customers who opted out, the user may find that partof the coding relating to the sending of marketing emails contains anerror that is resulting in marketing emails being sent to customers whoopted out of receiving marketing emails. The user or another user canmodify the coding to eliminate the error. The user can report back tothe exception component 1122 or remediation component 1118 that theanomaly issue has been resolved or remediated. In response, theremediation component 1118 can close out the file on the exceptionticket relating to that anomaly, noting that the anomaly issue wasresolved or remediated. If, instead, the user determines that theanomaly issue is not valid or otherwise does not have to be remediated,the user can report back to the exception component 1122 or remediationcomponent 1118 that the anomaly issue was not valid or otherwise did nothave to be remediated. In response, the remediation component 1118 canclose out the file on the exception ticket relating to that anomaly,noting that the anomaly issue was determined to not be valid or it wasdetermined that the anomaly did not have to be remediated.

In certain embodiments, the system 1100 can comprise a representationalstate transfer (REST) API component 1126 that can comprise a set ofRESTful APIs that can be web service APIs (e.g., HTTP-based APIs) thatcan follow or comply with certain REST architectural constraints. TheREST architectural constraints can be or can comprise certain rules thatcan allow programs to communicate with each other, wherein, for example,an API can be created on a server and a client device (e.g.,communication device) can communicate with the API on the server. Forinstance, the set of RESTful APIs can enable users to access content ofa website or a platform(s) (e.g., DLDP 102, or governance component 404,etc.) using their client devices to communicate with the APIs of orassociated with the governance component 404 or other components of thesystem 1100.

In some embodiments, the system 1100 can include a bug trackingcomponent 1128 that can comprise various desired bug tracking tools thatcan enable users to detect, identify, record, and/or track bugs (e.g., acomputer software, firmware, or hardware error, flaw, or fault) orpotential bugs in a computer-based system. The bug tracking toolsemployed by the bug tracking component 1128 can comprise, for example,Jira bug tracking tools, Flowable bug tracking tools, or other desiredbug tracking tools that can enable users (e.g., software developers orprogrammers) detect, identify, record, and/or track bugs or potentialbugs in the DLDP 102 and its constituent or associated components (e.g.,rights management component 402, governance component 404, or scannercomponent(s) (e.g., 124, 208, or 210), etc.), and can facilitatecorrecting or eliminating bugs in the DLDP 102 and its constituent orassociated components. In some embodiments, one or more of the bugtracking tools employed by the bug tracking component 1128 can beopen-source bug tracking tools.

Referring to FIG. 16 (along with FIGS. 1, 2, 4, and 11), FIG. 16illustrates a diagram of an example governance flow 1600 for governingthe collecting, processing, accessing, storing, sharing, and utilizationof data of users and information relating to data of users, inaccordance with various aspects and embodiments of the disclosed subjectmatter. In some embodiments, the governance component 404 can employ theexample governance flow 1600 to facilitate governing the collecting,processing, accessing, storing, sharing, and utilization of data ofusers, in accordance with the defined data management criteria, whichcan correspond to and/or be based at least in part on respective lawsand regulations of respective jurisdictions and/or respective agreementsbetween entities (e.g., between organizations and users, such ascustomers). The governance component 404 can evaluate KRI metrics 1602associated with source platforms 1604 and privacy principles 1606, suchas more fully described herein. The privacy principles 1606 can be basedat least in part on the laws, regulations, and/or agreements.

The source platforms 1604 can comprise, for example, the data lifecyclediscovery platform (DLDP) 1608, data subject rights platform 1610,consent management platform 1612, third party assessment platform 1614,custom sources 1616, and/or other platforms (e.g., governance component404), such as described herein. The DLDP 102 can manage discovery,scanning, storing, and/or processing of data, such as described herein.The data subject rights platform 1610 can manage data subject rights ofusers (e.g., customers) with regard to their data, access to data ofusers (e.g., access of users to their personal information),modification of data by users, etc., as more fully described herein. Theconsent management platform 1612 can manage consent of users to allowentities (e.g., organizations) to collect, process, access, store,share, and utilize data of users, send electronic communications (e.g.,emails, text messages, or phone calls) to users, consent to use cookieswith regard to users, etc., such as more fully described herein. Thethird party assessment platform 1614 can manage sharing of data of userswith third party entities and performing assessments (e.g., privacyand/or risk assessments, such as IRAs or PRAs) relating to sharing ofdata of users with third party entities, such as described herein.Custom sources 1616 can comprise modules or platforms that can be addedto facilitate collecting, processing, accessing, storing, sharing, andutilizing of data of users.

The privacy principles 1606 can comprise, for example, management 1618,notice and transparency 1620, choice and consents 1622, collection 1624,use, retain and dispose 1626, access 1628, third party disclosure 1630,security for privacy 1632, quality 1634, monitoring and enforcements1636, and/or another desired privacy principle, such as more fullydescribed herein. Respective privacy principles (e.g., 1620 through1636) of the privacy principles 1606 can be applicable or relevant torespective source platforms (e.g., 1608 through 1616) of the sourceplatforms 1604.

The rules engine 1638 can determine and generate the set of rules basedat least in part on applicable laws and regulations of jurisdictionsrelating to data protection, and applicable agreements relating to dataprotection, as more fully described herein. The rules engine 1638 canincorporate or take into account the privacy principles 1606, which canbe embodied in or derived from the laws, regulations, and/or agreements,when determining the rules of the set of rules. The rules engine 1638can comprise or be associated with a rules metastore 1640 (e.g., one ormore data stores) in which the rules engine 1638 can store the set ofrules, or information relating to the set of rules (e.g., informationrelating to the laws, regulations, and/or agreements; metadata;information relating to privacy principles 1606; or information relatingto source platforms 1604; etc.). The rules engine 1638 can structurevarious rules of the set of rules to have conditions (e.g., ruleconditions) that can be utilized to indicate when anomalies (e.g., dataprivacy anomalies or breaches) relating to data of users are or may beoccurring, wherein the rules engine 1638 can determine the conditions ofthe rules based at least in part on the obligations (e.g., obligationson the entity(ies)) that the rules engine 1638 can determine or derivefrom the laws, regulations, and/or agreements. The conditions in therules can relate to, for example, trend spikes 1642 in informationtrends relating to data of users, thresholds 1644 that can be employedto facilitate determining when conditions have been satisfied (e.g.,breached; met or exceeded), SLA configuration 1646 that can facilitatedetermining or implementing the conditions for the set of rules (e.g.,in accordance with an agreement, such as an SLA), and regulation 1648regarding the laws and regulations relating to data protection.

For instance, the rules engine 1638 can determine or formulate acondition in a rule to facilitate (e.g., enable) detecting a trend spike1642 in information relating to user data, wherein the trend spike 1642can indicate an anomaly that can or potentially can be a violation of anobligation (e.g., legal or contractual obligation) derived from anapplicable law, regulation, or agreement. The rules engine 1638 also candetermine thresholds 1644 that can be applied with regard to trendspikes 1642, time limits, data limits, consent limits, data retentionlimits, enforcement limits, notice limits, messaging limitations, and/orother conditions or limits relating to data protection, in accordancewith applicable laws, regulations, and/or agreements.

For example, the rules engine 1638 can determine a threshold 1644, suchas a defined threshold amount of time (e.g., 10 days, 15 days, 30 days,or other applicable amount of time) for completing a data subjectrequest, in accordance with an applicable law, regulation, or agreement,and can determine and formulate a rule that can include a condition andthe defined threshold amount of time, where the rule can indicate orspecify that a data subject request has to be completed within thedefined threshold amount of time after the data subject request has beenreceived by the entity (e.g., received by the website or platform of orassociated with the entity). As another example, the rules engine 1638can determine a threshold 1644, such as a defined threshold amount oftime (e.g., 10 days (e.g., 10 business days), 15 days, or otherapplicable amount of time) for discontinuing the sending of electroniccommunications to a user who has unsubscribed from or opted out ofreceiving the electronic communications, in accordance with anapplicable law, regulation, or agreement. The rules engine 1638 candetermine and formulate a rule that can include a condition and thedefined threshold amount of time for discontinuing the sending ofelectronic communications to a user, where the rule can indicate orspecify that the entity has to discontinue the sending of electroniccommunications to a user within the defined threshold amount of timeafter the request to unsubscribe or opt out has been received by theentity (e.g., received by the website or platform of or associated withthe entity).

The set of rules determined and generated by the rules engine 1638 canbe provided or made available to a validation engine 1650 (e.g.,validation component 1114), as part of the governance flow 1600. Thevalidation engine 1650 can utilize and apply respective (e.g.,applicable) rules (e.g., first subset of rules, or second subset ofrules, etc.) of the set of rules to respective entities associated withrespective jurisdictions, as more fully described herein. The validationengine 1650 can be associated with (e.g., communicatively connected to,interfaced with) the source systems 1652 (e.g., first set of data stores104, 106, and 108; or second set of data stores 202, 204, and 206; etc.)associated with respective entities as well as the various platforms(e.g., source platforms 1604) to facilitate monitoring and tracking thecollecting, processing, accessing, storing, sharing, and utilization ofdata of users by the source systems 1652 associated with the entitiesand the various platforms. In connection with the monitoring andtracking, the validation engine 1650 can apply the respective rules ofthe set of rules to the respective source systems 1652 associated withthe respective entities and the platforms to validate or verify whetherthe respective source systems 1652 and/or platforms are in compliancewith applicable rules of the set of rules or whether there exist anyanomalies relating to data protection associated with the collecting,processing, accessing, storing, sharing, and utilization of data ofusers. For instance, the validation engine 1650 can apply the respectiverules of the set of rules to the respective source systems 1652associated with the respective entities and the platforms to determinewhether the respective source systems 1652 and/or platforms are incompliance with applicable rules of the set of rules or are innon-compliance with any applicable rules of the set of rules; if innon-compliance, determine to what extent a source system 1652 orplatform is in non-compliance and the type(s) of non-compliance; and/ordetermine other anomalies or potential anomalies associated with thecollecting, processing, accessing, storing, sharing, and utilization ofdata of users, such as more fully described herein.

As part of the governance flow 1600, if the validation engine 1650detects an anomaly (e.g., a non-compliance or potential non-complianceissue or other anomaly, such as, for example, a privacy violation)during the validation process, the validation engine 1650 cancommunicate a message 1654, comprising information relating to theanomaly, to the notification engine 1656. For instance, the message 1654can be received and stored in an alert metastore 1658 of or associatedwith the notification engine 1656. The notification engine 1656 cananalyze the information relating to the anomaly contained in the message1654. Based at least in part on the analysis of the information relatingto the anomaly, the notification engine 1656 can generate an alertticket 1660 (e.g., exception or alert ticket) that can compriseinformation (e.g., details) regarding the anomaly and a request tovalidate the anomaly and, if there is an actual problem, remediate orresolve the anomaly, as more fully described herein. The notificationengine 1656 can communicate the alert ticket 1660 to an appropriate user1662 (e.g., service representative, such as a product and privacyrepresentative involved in validating and resolving anomalies).

After the user 1662 has validated and/or resolved the anomaly orpotential anomaly identified in the alert ticket 1660, the user 1662 cancommunicate with the notification engine 1656 or other component of thegovernance platform to inform (e.g., provide update or remediationinformation to) the notification engine 1656 or other component of thegovernance platform that the alert ticket 1660 has been addressed (e.g.,the anomaly was validated and was resolved or mitigated; or the anomalyturned out to not be valid). The notification engine 1656 (or othercomponent of the governance platform) can send a message 1664,comprising the update or remediation information, to the validationengine 1650 to inform the validation engine 1650 that the alert ticket1660 has been addressed.

Referring to FIG. 17 (along with FIGS. 1, 2, 4, and 11), FIG. 17illustrates a diagram of an example user interface 1700 of a privacy hubthat can provide information regarding KRI metrics associated withprivacy principles, risk scores, a privacy health index, and otherinformation, in accordance with various aspects and embodiments of thedisclosed subject matter. The example user interface 1700 can compriseinformation that can be generated by the governance component 404. Thegovernance component 404 and user interface component 128 can provide orfacilitate providing the example user interface 1700 to a communicationdevice (e.g., client device), such as communication device 138, forviewing by an authorized user.

The example user interface 1700 can be part of a privacy hub of orassociated with the governance component 404, and can be generated bythe governance component 404 in response to selection of the privacy hubbutton 1702. The example user interface 1700 can comprise, for example,KRI metrics 1704 by privacy principle. For instance, the user can selecta category filter 1706 for privacy principle. Based at least in part onthe selected category filter 1706 of privacy principle, the governancecomponent 404 can provide various KRI metrics 1704 associated withvarious privacy principles. The privacy principles can comprise, forexample, collection 1708, notice and transparency 1710, use, retain anddispose 1712, quality 1714, monitoring and enforcement 1716, management1718, access 1720, third party disclosure 1722, choice and consents1724, and security for privacy 1726, such as more fully describedherein.

The KRI metrics regarding collection 1708 can indicate, for example, anumber (e.g., 3) of flows that have been detected over collectingpersonal data of users. The governance component 404 also can provideother desired KRI metrics data regarding collection 1708 via the userinterface 1700 or another user interface as well. The KRI metricsregarding notice and transparency 1710 can indicate, for example, thatthere have been zero privacy statement link disruptions detected (e.g.,over a defined period of time, or since that KRI metric was lastchecked). Thus, there has been no detection of a disruption of the linkto the privacy statement that is to be provided to users. As desired,the governance component 404 also can provide other desired KRI metricsdata regarding notice and transparency 1710 via the user interface 1700or another user interface.

The KRI metrics regarding use, retain and dispose 1712 can indicate, forexample, a percentage (e.g., 70%) of personal data scan coverageperformed on a set of data stores (e.g., data stores 104, 106, and 108)associated with an entity (e.g., over a defined period of time, or sincethat KRI metric was last checked). As desired, the governance component404 also can provide other desired KRI metrics data regarding use,retain and dispose 1712 via the user interface 1700 or another userinterface. For example, the user interface 1700 indicates that there aretwo items of KRI metrics data regarding use, retain and dispose 1712 (asindicated at reference numeral 1728). The user can select the button foruse, retain and dispose 1712 to access and view a second item of KRImetrics data regarding use, retain and dispose 1712 (e.g., a second itemthat can indicate which particular data stores, or portions thereof,have been scanned for personal data of users, and/or indicate whichparticular data stores, or portions thereof, remain to be scanned forpersonal data).

The KRI metrics regarding quality 1714 can indicate, for example, apercentage (e.g., 80%) of personal data detection accuracy attained viathe scanning of the set of data stores (e.g., data stores 104, 106, and108) associated with the entity. As desired, the governance component404 also can provide other desired KRI metrics data regarding quality1714 via the user interface 1700 or another user interface.

The KRI metrics regarding monitoring and enforcement 1716 can indicate,for example, a number (e.g., 15) of privacy complaints from a regulator(e.g., data privacy regulator) in connection with the entity (e.g., overa defined period of time, or since that KRI metric was last checked).The governance component 404 also can provide other desired KRI metricsdata regarding monitoring and enforcement 1716 via the user interface1700 or another user interface as well.

The KRI metrics regarding management 1718 can indicate, for example, anumber (e.g., 0) of PIAs that have a “moderately high” or “high” riskrating. As desired, the governance component 404 also can provide otherdesired KRI metrics data regarding management 1718 via the userinterface 1700 or another user interface. For example, the userinterface 1700 indicates that there are two items of KRI metrics dataregarding management 1718 (as indicated at reference numeral 1730). Theuser can select the button for management 1718 to access and view asecond item of KRI metrics data regarding management 1718.

The KRI metrics regarding access 1720 can indicate, for example, that anumber (e.g., 8) of data subject requests exceeding the completiondeadline in connection with the entity. As desired, the governancecomponent 404 also can provide other desired KRI metrics data regardingaccess 1720 via the user interface 1700 or another user interface.

The KRI metrics regarding third party disclosure 1722 can indicate, forexample, a number (e.g., 0) of privacy complaints from the regulatorregarding sharing of data of users with third party entities, inconnection with the entity. As desired, the governance component 404also can provide other desired KRI metrics data regarding third partydisclosure 1722 via the user interface 1700 or another user interface.

The KRI metrics regarding choice and consents 1724 can indicate, forexample, a number (e.g., 1280) of marketing communication discrepanciesin connection with the entity. As desired, the governance component 404also can provide other desired KRI metrics data regarding choice andconsents 1724 via the user interface 1700 or another user interface.

The KRI metrics regarding security for privacy 1726 can indicate, forexample, a number (e.g., 10) of incidents classified as data breachassociated with an entity (e.g., over a defined period of time, or sincethat KRI metric was last checked). As desired, the governance component404 also can provide other desired KRI metrics data regarding securityfor privacy 1726 via the user interface 1700 or another user interface.For example, the user interface 1700 indicates that there are four itemsof KRI metrics data regarding security for privacy 1726 (as indicated atreference numeral 1732). The user can select the button for security forprivacy 1726 to access and view a second, third, or fourth item of KRImetrics data regarding security for privacy 1726.

In some embodiments, the governance component 404 can present, via theuser interface 1700, various risk scores 1734 for various platformsand/or privacy principles. For example, the governance component 404 canpresent, via the user interface 1700, a risk score (e.g., 23) for DSR1736, a risk score (e.g., 37) for DLDP 1738, a risk score (e.g., 10) forconsents 1740, a risk score (e.g., 76) for governance 1742 (e.g.,governance platform), and/or other risk scores. The governance component404 also can present, via the user interface 1700, a privacy healthindex (e.g., 89%) 1744 associated with an entity. The governancecomponent 404 also can present, via the user interface 1700, also canindicate the percentage (e.g., down 3%) of change 1746 in the privacyhealth index (e.g., over a defined period of time, or since that KRImetric was last checked).

In certain embodiments, the governance component 404 can present, viathe user interface 1700, can present other information (e.g.,governance-related information), such as information regarding a number(e.g., 14) of open issues 1748. The governance component 404 also canpresent, via the user interface 1700, the respective importance levels1750 (e.g., low, medium, and high priority or risk levels) of the openissues, and the respective numbers or percentages of open issues at therespective importance levels 1750.

The user also can select an overview button 1752 to obtain overviewinformation relating to governance issues. In response, the governancecomponent 404 can present, via the user interface 1700 or anotherinterface, the overview information relating to governance issuesrelating to data of users to the user. As desired, the user also canselect a privacy insights button 1754 to access privacy insightsinformation relating to governance. In response, the governancecomponent 404 can present, via the user interface 1700 or anotherinterface, the privacy insights information relating to governance tothe user. The user also can select an analytics button 1756 to accessanalytics information relating to governance. In response to selectionof the analytics button 1756, the governance component 404 can generateanalytics information relating to various analytics performed on data ofusers and/or information relating to management of data of users (or canaccess previously generated analytics information), and can present, viathe user interface 1700 or another interface, the analytics informationto the user.

Turning to FIG. 18 (along with FIGS. 1, 2, 4, and 11), FIG. 18 depicts adiagram of an example user interface 1800 that can provide variousinformation regarding data subject requests of users, in accordance withvarious aspects and embodiments of the disclosed subject matter. Thegovernance component 404 can determine and generate the various types ofinformation regarding data subject requests of users, based at least inpart on an analysis of data of users and/or information relating tomanagement of data of users, including information relating to theprocessing of data subject requests of users. In the example userinterface 1800, DSR exceeding SLA 1802 has been selected, and the userinterface 1800 is presenting various items of information relating toDSRs that have exceeded the SLA (e.g., exceeded the time limit tocomplete DSRs of users, as such time limit is specified by the SLA). Asdesired, a user also can select DSR fulfillment issues 1804 to obtaininformation regarding issues that exist with regarding to fulfilling DSRrequests or incomplete data access requests (DARs) 1806 to obtaininformation relating to incomplete DARs.

With further regard to DSR exceeding SLA 1802, the user interface 1800can present a risk score (e.g., 63/100) 1808 associated with DSRs withregard to an entity, as determined by the governance component 404. Theuser interface 1800 also can present a total number (e.g., 3562) ofrequests 1810 that can provide the total number of DSR requests duringthe defined time period, and the percentage (e.g., up 20%) of weeklychange 1812 in the total number of DSR requests, as determined by thegovernance component 404. The user interface 1800 can present a number(e.g., 120) of SLA exceptions 1814 that can indicate the number ofexception incidents relating to DSRs (e.g., a number of exceptionincidents due to DSRs not being completed within the time limit providedin the SLA) during the defined time period, and the percentage (e.g.,down 18%) of weekly change 1816 in the number of SLA exceptions, asdetermined by the governance component 404. The user interface 1800further can present a total number (e.g., 129) of alerts 1818 that canindicate the total number of alerts relating to DSRs during the definedtime period, and the percentage (e.g., down 6%) of weekly change 1820 inthe number of alerts, as determined by the governance component 404.

The example user interface 1800 also can provide a graph of the numberof DSR requests 1822, which, as depicted, can present informationregarding the number of DSR requests per week and the number of SLAexceptions per week, over a given time period (e.g., December andJanuary), as such information has been determined by the governancecomponent 404. As desired, the user can view a graph of the number ofDSR requests per day or per month.

The governance component 404 also can determine, and the example userinterface 1800 can present, information regarding DSR requests bycategory 1824, including information regarding data access requests 1826(e.g., number of data access requests and number of SLA exceptionsregarding data access requests), information regarding data erasurerequests 1828 (e.g., number of data erasure requests and number of SLAexceptions regarding data erasure requests), information regardingobjections to processing 1830 DSRs (e.g., number of objections toprocessing DSRs and number of SLA exceptions regarding objections toprocessing DSRs), information regarding data change requests 1832 (e.g.,number of data change requests and number of SLA exceptions regardingdata change requests), and information regarding other requests 1834(e.g., number of other types of requests and number of SLA exceptionsregarding the other requests). The governance component 404 further candetermine, and the example user interface 1800 can present, informationregarding other categories 1836 relating to DSRs, including a number ofSLA exceptions relating to rejection to processing DSRs, a number of SLAexceptions relating to DSRs, a number of SLA exceptions relating to dataprotection requests, and a number of SLA exceptions with regard toobjection to access.

In some embodiments, the governance component 404 can determine, and theexample user interface 1800 can present, DSR ticket details 1838relating to exception tickets for exception incidents relating to DSRsduring the given time period. The DSR ticket details 1838 can comprise anumber (e.g., 120) of DSR tickets 1840 during the given time period. TheDSR ticket details 1838 also can present specific information regardingindividual DSR tickets, including, for example, a ticket number 1842 ofDSR tickets, an alert number 1844 of DSR tickets, a DSR category 1846 ofthe DSR tickets (e.g., data access, data erasure, or objection, etc.), areceived date 1848 that can indicate the date a DSR ticket was received,a resolved date 1850 that can indicate the date a DSR ticket wasresolved, a country 1852 associated with the DSR ticket (e.g., thecountry where the DSR-related exception occurred), and a number of daysto resolve 1854 the SLA exceptions relating to DSRs.

Referring briefly to FIG. 19 (along with FIGS. 4 and 11), FIG. 19presents a diagram of example graphs 1900 that can provide informationregarding certain opt in and opt out trends, in accordance with variousaspects and embodiments of the disclosed subject matter. The governancecomponent 404 can determine and generate the information regarding optin and opt out trends, based at least in part on an analysis ofinformation that can indicate, for example, when users (e.g., customers)have opted in to receiving electronic communications from an entity andwhen users have opted out of receiving electronic communications fromthe entity, with regard to a given time period.

The example graphs 1900 can comprise an opt in/opt out trend graph 1902and a preference metric trend graph 1904. The opt in/opt out trend graph1902 can comprise opt in data 1906 (e.g., in graphical form) that canindicate the total number of users who have opted in to receivingelectronic communications from the entity for each month during thegiven time period and opt out data 1908 (e.g., in graphical form) thatcan indicate the total number of users who have opted out of receivingelectronic communications from the entity for each month during thegiven time period.

The preference metric trend graph 1904 can comprise monthly opt in data1910 (e.g., in graphical form) that can indicate, for each month duringthe given time period, the number of users who have opted in toreceiving electronic communications from the entity during that monthand monthly opt out data 1912 (e.g., in graphical form) that canindicate, for each month during the given time period, the number ofusers who have opted out of receiving electronic communications from theentity during that month. As can be observed from the preference metrictrend graph 1904, the governance component 404 can identify, and thepreference metric trend graph 1904 can show, any abnormal spikes, suchas graph region 1914, in the user opt in/opt out trend, wherein thegraph region 1914 can indicate an abnormal spike in the opt in trenddata during April and May. If the governance component 404 (e.g.,validation component 1114 of the governance component 404) determinesthat an abnormal spike in the number of users opting in during aparticular month(s) exceeds a defined threshold number of opt in users,as provided in an applicable rule of the set of rules (e.g., a rule thatapplies to the entity), the governance component 404 can generate anexception ticket regarding the anomaly (e.g., the abnormal spike) toinitiate validation and/or remediation of the anomaly issue, as morefully described herein.

Turning briefly to FIG. 20 (along with FIGS. 4 and 11), FIG. 20 presentsa diagram of an example graph 2000 that can provide informationregarding marketing opt-out exception incidents in relation to totalemail messages sent by an entity during a given time period, inaccordance with various aspects and embodiments of the disclosed subjectmatter. The governance component 404 can determine and generate theinformation regarding the marketing opt-out exception incidents inrelation to the total email messages sent by the entity during the giventime period, based at least in part on an analysis of informationregarding emails sent to users by the entity each month and exceptiontickets relating to the sending of emails to users by the entity eachmonth, during the given time period.

The graph 2000 can comprise email count data 2002 (e.g., in graphicalform) that can indicate, for each month during the given time period,the total number of emails sent to users by the entity during the month.The graph 2000 also can comprise exception email count data 2004 (e.g.,in graphical form) that can indicate, for each month during the giventime period, the total number of exception tickets regarding exceptionincidents arising out of emails improperly sent, or at least potentiallyimproperly sent, to users by the entity during the month. As can beobserved from the graph 2000, the number of exception tickets generatedeach month is relatively and desirably low and also is relatively anddesirable steady (e.g., no abnormal spikes).

Referring briefly to FIG. 21 (along with FIGS. 4 and 11), FIG. 21presents a diagram of an example graph 2100 that can provide informationregarding cookie consents of users associated with an entity in relationto consents associated with unregistered countries during a given timeperiod, in accordance with various aspects and embodiments of thedisclosed subject matter. The governance component 404 can determine andgenerate the information regarding the cookie consents (e.g., cookieacceptances) of users associated with the entity in relation to consentsassociated with unregistered countries during the given time period,based at least in part on an analysis of information regarding cookieconsents of users associated with entity accounts each month andinformation regarding consents usage from unregistered countries eachmonth, during the given time period.

The graph 2100 can comprise entity account consent data 2102 (e.g., ingraphical form) that can indicate, for each month during the given timeperiod, the percentage of population (e.g., users) who consented forcookies with regard to the entity during the month. The graph 2100 alsocan comprise usage from unregistered country data 2104 (e.g., ingraphical form) that can indicate, for each month during the given timeperiod, a percentage of population who consented for cookies with regardto unregistered countries during the month. As can be observed from thegraph 2100, the percentage of population (e.g., users) who consented forcookies with regard to the entity for each month of the given timeperiod is relatively and desirably high (e.g., at or almost 100%) andalso is relatively and desirable steady (e.g., no abnormal dips (e.g.,declines) in the percentage). As also can be observed from the graph2100, the percentage of population who consented for cookies with regardto unregistered countries for each month of the given time period isrelatively and desirably low (e.g., relatively close to 0%) and also isrelatively and desirable steady (e.g., no abnormal spikes in thepercentage).

Turning briefly to FIG. 22 (along with FIGS. 4 and 11), FIG. 22 presentsa diagram of an example graph 2200 that can provide informationregarding a personalization trend within an entity and third partyentities during a given time period, in accordance with various aspectsand embodiments of the disclosed subject matter. The governancecomponent 404 can determine and generate the information regarding thepersonalization trend associated with personalization with regard tousers (e.g., customers) within the entity and third party entities(e.g., third party merchants) during the given time period, based atleast in part on an analysis of information relating to personalizationassociated with users (e.g., personalization of experience for usersthrough the tracking, collection, and use of personal data of users)within the entity and third party entities each month, during the giventime period.

The graph 2200 can comprise entity-related customer personalizationcount data 2202 (e.g., in graphical form) that can indicate, for eachmonth during the given time period, the number of customers (e.g.,users) who consented to personalization (e.g., by giving one or moreconsents to allow the entity to track, collect, and use their personaldata) with the entity during the month. The graph 2200 also can comprisethird party entity-related customer personalization count data 2204(e.g., in graphical form) that can indicate, for each month during thegiven time period, the number of customers who consented topersonalization with third party entities during the month. As can beobserved from the graph 2200, the number of customers who consented topersonalization with the entity for each month is substantiallyconsistent with the number of customers who consented to personalizationwith third party entities for that month. This can indicate that thereare no abnormalities, or at least it is likely that there are noabnormalities, with regard to personalization for users within theentity or personalization for users within third party entities. Hadthere been a significant difference between the entity-related customerpersonalization count data 2202 and the third party entity-relatedcustomer personalization count data 2204 for a particular month, suchsignificant difference may have been an indication that there was anabnormality with regard to personalization for users within the entityand/or with regard to personalization for users within third partyentities.

FIG. 23 depicts a block diagram of an example system 2300 that can beemployed by the DLDP and its constituent or associated platforms tofacilitate managing data of users, in accordance with various aspectsand embodiments of the disclosed subject matter. The system 2300 canhave a modular design that can enable flexibility to develop and rollout individual components as separate modules. The modular design ofsystem 2300 can enable targeted adaptation of modules for externalenvironments. The decoupled architecture, which can be enabled byemploying a modular design, can provide desirable flexibility to developinteroperable modules independently.

The system 2300 can comprise a user interface component 2302 (UI) thatcan generate and provide various desired user interfaces that can enableusers, when authenticated and as permitted, to access, perceive (e.g.,view, hear, or otherwise experience), and retrieve data, including theirdata and information relating to their data, and/or data of other usersand information relating to data of other users. The various desireduser interfaces can comprise, for example, the various user interfacesdescribed herein.

The system 2300 can employ desirable authentication protocols,technologies, and algorithms to facilitate secure authentication ofusers attempting to access the DLDP and its constituent or associatedplatforms, and access data of or relating to users. In accordance withvarious embodiments, the system 2300 can comprise single sign-on andtwo-factor authentication component 2304 (SSO-2FA). Single sign on canallow users to authenticate with and gain access to the DLDP, itsconstituent or associated platforms, and/or associated applicationsthrough a single log in by presenting appropriate (e.g., valid)authentication credentials (e.g., username, password, passcode, personalidentification number (PIN), or biometric identification information,etc.). Two-factor authentication (or multi-factor authentication) canallow users to authenticate with and gain access to the DLDP, itsconstituent or associated platforms, and/or associated applicationsthrough a two-factor (or multi-factor) authentication process bypresenting two (or more) types of appropriate authentication credentials(e.g., username/password, passcode, personal identification number(PIN), biometric identification information, authentication token orkey, authentication credentials via a device, such as a smart phone, oruser providing answers to personal questions, etc.).

The system 2300 can employ an API component 2306 (API) that can comprisevarious APIs that can be utilized to enable desirable interfacing andcommunication of information between various components (e.g., securedata store, UI component, data management component, governanceplatform, rights management platform, or notification component, etc.)of or associated with the DLDP, in accordance with various protocols anddata formats supported by the API component 2306, such as describedherein.

The system 2300 also can employ an open authorization component 2308(OAUTH) that can provide applications, websites, and services, whenauthorized and/or authenticated, secure designated access to data ofusers. The OAUTH 2308 can be or comprise an open-standard authorizationprotocol or framework that can enable an application, website, orservice, when authorized by a user, to access data of the user via theDLDP, its constituent or associated platforms (e.g., governanceplatform, or rights management platform, etc.), or associated datastores, without the user having to provide the application, website, orservice the user's authentication credentials. In certain embodiments,the application, website, or service can utilize an authorization tokento prove its identity and prove that it is authorized to access the dataof the user via the DLDP, its constituent or associated platforms, orassociated data stores.

The system 2300 can comprise an ETL component 2310 (ETL) that can employan ETL process (e.g., ETL batch process) and/or can comprise an ETLserver that can utilize an ETL process, wherein the ETL process and/orETL server can facilitate reading and transferring scan results from ascanner component of or associated with the DLDP to the batch servercomponent. The ETL process of the ETL component 2310 can integrate orcombine data from multiple data sources into a single, consistent set ofdata that can be stored in a desired data store or communicated to adesired component of or associated with the DLDP. During the extractionoperation of the ETL process, data can be copied and/or communicatedfrom the source locations of the data to a staging area, wherein thedata can be structured data or unstructured data (e.g., informationcontained in or associated with emails; image data (e.g., visual images,such as digital images, photographs, video images, or other type ofimage data); or other type of unstructured data), and wherein the sourcelocations (e.g., server, data store, system, file, email, or web page,etc.) can be structured or unstructured. In the staging area, theextracted data (e.g., raw data) can be transformed to convert or formatthe data to a form that can be useful or suitable for analysis (e.g., bythe DLDP, governance platform, or rights management platform, etc.) orto conform to a schema of a data store (e.g., relational database storedin a data store) in which the transformed data can be stored. Thetransformation of the data can comprise, for example, formatting,filtering, validating, authenticating, translating, summarizing,performing calculations on, encrypting or performing a data security orcryptographic process on, and/or normalizing the data. During the loadoperation, the transformed data can be transferred from the stage areato the target destination, which can be a data store or a component ofor associated with the DLDP.

The system 2300 also can include an authentication component 2312 (AUTH)that can employ desired authentication protocols, techniques, keys, oralgorithms, for example, in connection with the ETL component 2310. Theauthentication component 2312 can be employed to authenticate dataduring the transformation operation and/or authenticate with a componentor interface (e.g., API) during the extraction operation to extract datavia a component or interface.

The system 2300 also can include a monitoring component 2314 that canmonitor activity, data traffic, operations, etc., of or associated withthe DLDP, its constituent or associated platforms, data storesassociated with the DLDP, or other components (e.g., scanner component,docker component, bug tracking component, or artificial intelligencecomponent, etc.), devices (e.g., communication device), or systemsassociated with the DLDP. For instance, the monitoring component 2314can monitor operations, activity, and data traffic associated with theUI component 2302, API component 2306, and ETL component 2310, as wellas other desired components.

The system 2300 further can comprise a logging component 2316 that canlog information relating to events of or associated with the DLDP, itsconstituent or associated platforms, data stores associated with theDLDP, or other components, devices, or systems associated with the DLDP.The logging component 2316 can log the time of an event, operations thatwere performed during or in connection with an event, errors associatedwith an event, components or devices associated with an event, or otherdesired information relating to an event. The logging component 2316 canstore the information relating to events in log files, which can bestored in a desired data store.

The code for UI component 2302, API component 2306, and the common dataprivacy model employed by the system 2300 (e.g., employed by the DLDPand its constituent or associated platforms) can be independentlydesigned to enable the relevant modules to be changed, modified, orreplaced to enhance the performance, operation, and functionality of themodules employed in the system 2300 and, accordingly, enhance theperformance, operation, and functionality of the system 2300 overall.

FIG. 24 depicts a block diagram of an example system 2400 that cancomprise a DLDP that can utilize containerized application technology,in accordance with various aspects and embodiments of the disclosedsubject matter. The example system 2400 can comprise a DLDP 2402 thatcan perform data discovery and data tracking in a secure and efficientmanner to facilitate desirable data protection of the data of users andinformation relating thereto, in accordance with the defined datamanagement criteria, as more fully described herein. Every module of theapplication employed by the DLDP 2402 can be deployed as a container.Based on the infrastructure capacity of or associated with the system2400, including the DLDP 2402, the deployment of the modules of theapplication as containers can be desirably bundled to enable moreefficient use of the resources of the system 2400. The DLDP 2402 oranother component associated therewith can generate and maintain aconfiguration file that can comprise information relating to, and thatcan define, application dependencies and deployment (e.g., deployment ofmodules of the application as containers), and can utilize (e.g.,execute) the configuration file for automated deployment of the modulesof the application as containers.

The DLDP 2402 can comprise the UI component 2302, API component 2306,ETL component 2310, and authentication component 2312, and/or othercomponents, and each component can comprise respective functionality,such as more fully described herein. The system 2400 can includeinfrastructure 2404 that can be utilized to implement and provideresources to the DLDP 2402 and other components, devices, or sub-systemsof the system 2400 to enable the operation of the DLDP 2402 and theother components, devices, or sub-systems of the system 2400. In someembodiments, the infrastructure 2404 can comprise one or more computersystems, servers, interfaces, and/or peripheral components, etc., thatcan provide the desired resources to the DLDP 2402 and other components,devices, or sub-systems of the system 2400, wherein the one or morecomputer systems, servers, interfaces, and/or peripheral components,etc., can be as more fully described herein. In some embodiments, all orpart of the system 2400, including all or part of the infrastructure2404, can be located in a cloud computing environment.

The system 2400 also can comprise a host operating system 2406 that canbe associated with and can operate on the infrastructure 2404. The hostoperating system 2406 can comprise software components (e.g., softwarecode) that can interact with on operate on the infrastructure 2404(e.g., computer hardware of the infrastructure 2404) to facilitateperforming various computing operations. The host operating system 2406can be the primary operating system that can be installed on a harddrive of the computer (e.g., of the infrastructure 2404). In someembodiments, the system 2400 also can comprise one or more virtualoperating systems (not shown) that can operate within or in associationwith the host operating system 2406. The host operating system 2406 canutilize container-based virtualization, wherein modules of theapplication(s) can be deployed as containers, such as described herein.Containers can allow applications on a server to share the sameoperating system kernel, while also still being able to providedesirable hardware isolation between the applications.

The system 2400 further can comprise a docker component 2408 that can beassociated with and can operate on the host operating system 2406. Thedocker component 2408 can comprise all or a desired portion of thedocker functionality of the docker host, docker image, docker registry,docker pull, docker build, docker run, and/or docker file, etc., tofacilitate generating and implementing desired containers (e.g., dockercontainers) for applications, such as more fully described herein. Inaccordance with various embodiments, one or more components of the DLDP2402, and/or its constituent or associated platforms (e.g., governanceplatform, or rights management platform, etc.), including, for example,all or part of the UI component 2302, API component 2306, ETL component2310, and/or authentication component 2312 can be implemented asindividual or independent containers.

FIG. 25 illustrates a block diagram of an example open source stack 2500that can be employed by the DLDP and its constituent or associatedplatforms, in accordance with various aspects and embodiments of thedisclosed subject matter. The DLDP and its constituent or associatedplatforms can be built or formed on an approved and supported opensource stack 2500 to take advantage of the cutting edge developments insoftware and infrastructure.

The open source stack can comprise a front tier 2502 that can include amobile application framework 2504, an application framework 2506, aprogramming language framework 2508, a testing framework for programming2510, and a node automation framework 2512. The mobile applicationframework 2504 can be utilized to develop applications (e.g., mobileapplications) for mobile devices and mobile device operating systemplatforms (e.g., iOS, Android, Web, or Universal Windows Platform(UWP)). In some embodiments, the mobile application framework 2504 canbe an open-source mobile application framework. The applicationframework 2506 can comprise a web application framework that can beutilized to develop web applications for communication devices (e.g.,computers, servers, Internet of Things (IoT) devices, or other devices).The programming language framework 2508 can employ a programminglanguage, a programming language engine, APIs, programming languagelibraries, and/or other components that can be utilized to facilitatedeveloping and running applications, such as web-based applications. Thetesting framework for programming 2510 can facilitate ensuringcorrectness or integrity of a programming codebase. The testingframework for programming 2510 can be utilized to generate tests thatcan be utilized to test the correctness or integrity of a programmingcodebase, wherein an API can be utilized to facilitate developing thetests. The node automation framework 2512 can be an open-source node.jsautomation framework comprising tools, including browser testing tools,that can be utilized to add automation to node.js web projects andapplications, for example, to facilitate testing of such web projectsand applications. In accordance with various embodiments, the front tier2502 can employ, for example, React Native, Paypal Kraken, JavaScript(JS), Jest, Nemo.js, and/or other desired frameworks. For instance, theuser interface component can utilize Kraken or another desired type ofapplication framework to facilitate generating and providing (e.g.,presenting) desired user interfaces.

The open source stack 2500 can include a middle tier 2514 that cancomprise a software platform 2516, a micro service framework 2518, aprogramming language framework 2520, and a testing framework 2522. Thesoftware platform 2516 can be utilized to develop applications anddeploy applications in a computing environment. The software platform2516 can be utilized in a variety of desired computing platforms. Themicro service framework 2518 can be utilized to create applications andassociated micro services. The micro service framework 2518 can be anopen source Java-based framework that can be used to develop the microservices. The programming language framework 2520 can comprise anopen-source data query and manipulation language that can be used forAPIs. The programming language framework 2520 can be utilized tofacilitate efficiently processing (e.g., responding to) queries andaccessing data and/or the related information from a desired data source(e.g., data store). The testing framework 2522 can be an open-sourcetesting framework that can be utilized for software platforms, such as,for example, Java. In accordance with various embodiments, the middletier 2514 can employ, for example, Java, Springboot, GraphQL, Mockito,and/or other desired platforms or frameworks. For instance, various APIsand services described herein can utilize open-source Java andSpringboot.

The open source stack 2500 also can include a database and ETL 2524,which can comprise a relational database management system 2526, adistributed graph database 2528, a workflow management platform 2530,and a programming language 2532. The relational database managementsystem 2526 can be utilized for relational databases, such as relationaldatabases that can be stored in a data store of an entity or in thesecure data store of the DLDP. In some embodiments, the relationaldatabase management system 2526 can be an open-source relationaldatabase management system. The distributed graph database 2528 can bean open-source, distributed, and/or scalable graph database that can beutilized for storing and querying graphs, including relatively largegraphs comprises a large number (e.g., thousands, millions, or billions)of vertices and edges distributed across a multi-machine cluster. Theworkflow management platform 2530 can be an open-source workflowmanagement platform that can programmatically author, schedule, andmonitor workflows and tasks, such as workflows or tasks of or associatedwith the DLDP or its constituent or associated platforms. Theprogramming language 2532 can be a desired high level and generalpurpose programming language. The programming language 2532 can be amulti-paradigm programming language that can support object-orientedprogramming, structured programming, functional programming, and/oraspect-oriented programming. In accordance with various embodiments, thedatabase and ETL 2524 can employ, for example, Percona server,JanusGraph, Apache Airflow, Python, and/or other desired database andETL functions, systems, and databases. For instance, the back end of theDLDP can employ open-source Percona for MySQL.

The open source stack 2500 can further comprise deployment andorchestration 2534 that can include cloud automation platform 2536, acloud computing services platform 2538, and a container orchestrationsystem 2540. The cloud automation platform 2536 can be used for processautomation, such as automation of business processes, and can comprise adesirable process management environment, which can include adesign-time environment and a runtime environment, wherein the processmanagement environment can include development, testing, production, andmanagement of processes that can be performed in the cloud. The cloudcomputing services platform 2538 can provide a suite of cloud computingservices, which can be modular cloud services that can include, forexample, various services relating to computing, data storage, dataanalytics, and machine learning, and also can provide various managementtools. The container orchestration system 2540 can be an open-sourcecontainer orchestration system that can automate application deployment,scaling, and management (e.g., management of containerized workloads andservices). For instance, the container orchestration system 2540 canfacilitate automating deployment, scaling, and operations of applicationcontainers. The container orchestration system 2540 can comprise avariety of services, support, and tools that can facilitate suchautomating of application deployment, scaling, and management. Inaccordance with various embodiments, the deployment and orchestration2534 can comprise and utilize Process Cloud Service (PCS), Google Cloud,Kubernetes, or other desired platforms and systems for deployment andorchestration associated with the DLDP and its constituent or associatedplatforms (e.g., governance platform, or rights management platform,etc.).

The system 2600 can provide a variety of benefits, such as, for example,desirable flexibility and agility in forming the DLDP and itsconstituent or associated platforms, cost effectiveness, utilization ofproductive and cutting edge industry technologies, and desirableexternalization.

FIG. 26 illustrates a block diagram of an example system 2600 that canemploy an API and server to facilitate enabling client applications anddevices to query and access data, to facilitate desirable processing andcommunication of data of users in connection with the DLDP, inaccordance with various aspects and embodiments of the disclosed subjectmatter. The system 2600 can comprise a data source 2602, which can be orcan comprise one or more data stores associated with an entity, such asdescribed herein. The data source 2602 can store data of users andinformation relating to the data of users (e.g., information derivedfrom the processing of data of users or otherwise based at least in parton the data of users). The system 2600 also can comprise a client device2604 that can comprise and/or utilize a client application to accessdata of users and/or information relating to the data of users from thedata source 2602, for example, as the client device 2604 or associateduser is permitted (e.g., authorized) to access such data and/or relatedinformation.

To enable desirable access to the data and/or related information, thesystem 2600 further can comprise an API server component 2606 that canbe associated with (e.g., communicatively connected to) the data source2602 and the client device 2604. The API server component 2606 can bepart of the DLDP (not shown in FIG. 26; and as more fully describedherein). In some embodiments, the API server component 2606 can be aGraphQL server that can utilize a GraphQL language, which can be anopen-source data query and manipulation language that can be used forAPIs of the system 2600, and can be utilized to facilitate processing(e.g., responding to) queries and accessing data and/or the relatedinformation from the data source 2602. In other embodiments, anotherdesired data query and data manipulation language and protocol can beutilized for the APIs of the system 2600. The user interfaces and APIsof the various modules of the DLDP and its constituent or associatedplatforms (e.g., governance component, or rights management component,etc.) can be integrated using GraphQL or other desired data query anddata manipulation language and protocol. Employing GraphQL or the otherdesired data query and data manipulation language and protocol canprovide a desirable (e.g., robust or powerful) capability to expose andmanipulate the underlying data from the data source 2602 to desirablysatisfy (e.g., to desirably suit or meet) the data, business, orpersonal demands (e.g., wants, desires, or needs) of users.

In response to a data request or query for data of users and/or relatedinformation received from the client device 2604, the API servercomponent 2606 can desirably process the data request or query toefficiently retrieve desired data of users and/or related informationthat can be responsive to the data request or query from the data source2602 (which can comprise one or more data sources in one or morelocations) without retrieving or providing extraneous or undesired data(or at least substantially minimizing or mitigating the retrieving andcommunicating of extraneous or undesired data) in response to the datarequest or query. The API server component 2606 can provide the desireddata and/or related information responsive to the data request or queryto the client device 2604.

Employing the API server component 2606 can provide a number ofbenefits. For instance, there can be increased API reusability. Therecan be no, or at least minimal, over-fetching and under-fetching of dataand/or related information from the data source 2602. The API servercomponent 2606, by employing GraphQL or other language and protocol, canallow users to select and choose the fields in the response object withregard to a data request or query. Since there can be no, or at leastminimal, over-fetching and under-fetching of data and/or relatedinformation from the data source 2602, network data traffic can bedesirably reduced. Another benefit can be that the API server component2606, by employing GraphQL or other language and protocol, can enablevalidation and type-checking of fields to be inbuilt. Also, there can bedesirable developer productivity through enhanced (e.g., improved,easier, or more efficient) API exploration. Tools, such as GraphQL orthe other desired language and protocol that can be employed by the APIserver component 2606, can enable developers to desirably (e.g., quicklyand efficiently) understand and be effective in using the APIs of thesystem 2600.

FIG. 27 depicts a block diagram of an example system 2700 that cansupport multiple tenant entities to facilitate desirably managing dataof users and information relating thereto with regard to multiple tenantentities associated with the DLDP, in accordance with various aspectsand embodiments of the disclosed subject matter. The system 2700 cancomprise a multi-tenant data store 2702 that can store data of usersand/or information relating to the data of users, which can be collectedor derived in connection with multiple tenant entities (e.g., multipleorganizations, business, or merchants), wherein respective users can beassociated with respective entities. The multi-tenant data store 2702can be associated with (e.g., communicatively connected to) or part ofthe DLDP, as more fully described herein. The multi-tenant data store2702 can be designed or structured to support a centralized dataaggregation model to facilitate supporting multiple tenant entities.

The system 2700 also can comprise an API component 2704 that can beassociated with (e.g., communicatively connected to) the multi-tenantdata store 2702. The API component 2704 can comprise various APIs thatcan be utilized to enable desirable interfacing and communication ofinformation between various components (e.g., secure data store, UIcomponent, data management component, governance platform, rightsmanagement platform, or notification component, etc.) of or associatedwith the DLDP (not shown in FIG. 27), in accordance with variousprotocols and data formats supported by the API component 2704, such asdescribed herein. The API component 2704 can employ GraphQL or otherdesired language and protocol to facilitate desirably (e.g.,efficiently) retrieving data of users and/or information relatingthereto from the multi-tenant data store 2702 in response to datarequests or queries from clients, such as more fully described herein.

The system 2700 can comprise multiple user interfaces, including userinterface component 2706, user interface component 2708, and userinterface component 2710, that can be associated with (e.g.,communicatively connected to) the API component 2704 and can berespectively associated with tenant entities, including entity 2712,entity 2714, and entity 2716. The user interface components (e.g., 2706,2708, and 2710, etc.) can generate and provide various desired userinterfaces that can enable the entities (e.g., 2712, 2714, and 2716,etc.), when authenticated and as permitted, to access, perceive (e.g.,view, hear, or otherwise experience), and retrieve data, includingrespective data of users that are associated with the respectiveentities (e.g., 2712, 2714, and 2716, etc.) and/or respectiveinformation relating to the respective data from the multi-tenant datastore 2702 via the API component 2704.

At various times, the respective entities (e.g., 2712, 2714, and 2716,etc.) can utilize the respective user interface components (e.g., 2706,2708, and 2710, etc.) to communicate respective data requests or queriesto the API component 2704 in order to request respective data of usersor respective information relating thereto. The API component 2704 canprocess the respective data requests or queries and, in response to therespective data requests or queries, can access the multi-tenant datastore 2702 to retrieve the respective data of users or respectiveinformation relating thereto from the multi-tenant data store 2702. Atthe various times, the API component 2704 can communicate the respectivedata of users or respective information relating thereto, which can berespectively responsive to the respective data requests or queries, tothe respective user interface components (e.g., 2706, 2708, and 2710,etc.) of the respective entities (e.g., 2712, 2714, and 2716, etc.).

The system 2700, by being able to support centralized data aggregationof multiple tenant entities, efficient processing of data requests orqueries, and efficient processing of data of users and informationrelating thereto, can provide a number of benefits. For instance, thesystem 2700 can provide a desirably streamlined deployment process, canenable desirable (e.g., easier or more efficient) applicationmaintenance, can facilitate desirable onboarding of new tenant entities,can desirably reduce data duplication, can enable desirable patching andupgrades, and can provide a single source (e.g., data source) of desireddata.

In view of the example systems and/or devices described herein, examplemethods that can be implemented in accordance with the disclosed subjectmatter can be further appreciated with reference to flowcharts in FIGS.28-34. For purposes of simplicity of explanation, example methodsdisclosed herein are presented and described as a series of acts;however, it is to be understood and appreciated that the disclosedsubject matter is not limited by the order of acts, as some acts mayoccur in different orders and/or concurrently with other acts from thatshown and described herein. For example, a method disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a method inaccordance with the subject specification. It should be furtherappreciated that the methods disclosed throughout the subjectspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methods to computersfor execution by a processor or for storage in a memory.

FIG. 28 depicts a flow diagram of an example, non-limiting method 2800that can desirably (e.g., efficiently or optimally) manage datadiscovery of data stored in data stores associated with one or moreentities to facilitate determining compliance of the data stores andentities with obligations arising out laws and/or agreements relating todata protection, in accordance with various aspects and embodimentsdescribed herein. The method 2800 can be employed by, for example, asystem comprising the DLDP, its constituent or associated platforms(e.g., governance platform), a processor component (e.g., of orassociated with the DLDP), and/or a data store (e.g., of or associatedwith the DLDP).

At 2802, discovery of the presence of items of data of users stored in aset of data stores can be managed, in accordance with the defined datamanagement criteria. At 2804, the items of data can be discovered in theset of data stores based at least in part on scanning of the set of datastores, in accordance with the management of the discovery, whereininformation relating to the items of data can be generated based atleast in part on the scanning. The data management component of orassociated with the DLDP can manage (e.g., control) the discovery (e.g.,detection) of the presence of items of data of users stored in the setof data stores associated with an entity, in accordance with the defineddata management criteria. A scanner component of or associated with theDLDP can scan the set of data stores and can detect the items of datastored in the set of data stores, based at least in part on thescanning. The scanner component, a machine learning component of orassociated with the DLDP, or the data management component can generatethe information relating to the items of data based at least in part onthe results (e.g., scanning results) of the scanning of the set of datastores.

At 2806, the information relating to the items of data and/or a portionof the items of data can be stored in a secure data store of the DLDP.The data management component can store the information relating to theitems of data and/or the portion of the items of data in the secure datastore of the DLDP.

At 2808, a determination can be made regarding compliance of the set ofdata stores with a set of obligations relating to data protection basedat least in part on the results of analyzing the information relating tothe items of data and/or the portion of the items of data. The datamanagement component can determine the compliance (e.g., the extent orlevel of compliance) of the set of data stores with the set ofobligations relating to data protection based at least in part on theresults of analyzing the information relating to the items of dataand/or the portion of the items of data.

In that regard, the data management component (e.g., the governancecomponent of the data management component) can analyze laws,regulations, and/or agreements determined to be applicable to the set ofdata stores, the one or more entities, and/or the users. For instance,the data management component can determine or identify a first subsetof laws, regulations, and/or agreements relating to data protection thatcan be applicable to the set of data stores. Based at least in part onthe results of analyzing the first subset of laws, regulations, and/oragreements, the data management component can determine the set ofobligations (e.g., legal and/or contractual requirements,responsibilities, duties, constraints, or provisions). The datamanagement component can determine a set of rules that can correspond tothe set of obligations and can be used to facilitate enforcing the setof obligations against the set of data stores, the DLDP, and/or theentity, and determining the extent or level of compliance of the set ofdata stores, the DLDP, and/or the entity with the set of obligations.The data management component can determine the compliance of the set ofdata stores, the DLDP, and/or the entity with the set of obligationsbased at least in part on the results of analyzing the informationrelating to the items of data, the portion of the items of data, and/orthe set of rules.

FIG. 29 illustrates a flow diagram of an example, non-limiting method2900 that can desirably (e.g., efficiently or optimally) determine a setof rights of a user with regard to data of the user that is stored in aset of data stores associated with an entity, in accordance with variousaspects and embodiments described herein. The method 2900 can beemployed by, for example, a system comprising the DLDP, its constituentor associated platforms (e.g., rights management platform, or governanceplatform, etc.), a processor component (e.g., of or associated with theDLDP), and/or a data store (e.g., of or associated with the DLDP).

At 2902, items of data of users can be detected in a set of data storesassociated with an entity based at least in part on the results ofscanning the set of data stores. At 2904, information relating to theitems of data can be determined based at least in part on the results ofthe scanning. A scanner component of or associated with the DLDP canscan the set of data stores. Based at least in part on the results ofscanning the set of data stores, the scanner component can detect theitems of data of the users that are stored in the set of data stores.The scanner component, machine learning component, or data managementcomponent can determine and generate the information relating to theitems of data based at least in part on the results of the scanning andanalysis of the scanning results.

At 2906, the information relating to the items of data and/or a portionof the items of data can be stored in a secure data store of the DLDP.The data management component can store the information relating to theitems of data and/or the portion of the items of data in the secure datastore of the DLDP.

At 2908, a set of rights of a user, with regard to a subset of theinformation and a subset of the items of data associated with the user,can be determined based at least in part on a set of rules, wherein theset of rules can be determined based at least in part on a setobligations associated with the set of data stores and related to dataprotection. The rights management platform can determine the set ofrights of the user (and the scope of the set of rights) with regard tothe subset of the information and the subset of the items of dataassociated with the user, based at least in part on the set of rules.The governance platform can determine the set of obligations based atleast in part on the results of analyzing a first subset of laws,regulations, and/or agreements determined to be applicable to the set ofdata stores and associated entity, at least with regard to the user. Thelaws and regulations of the first subset can be associated with at leasta first jurisdiction of the set of data stores and/or the entity, and/orcan be associated with the user. The agreement(s) in the first subsetcan be associated with the set of data stores, entity, and/or user.

The set of rights of the user can relate to, for example, one or more ofthe right to information, the right of access, the right ofrectification, the right of erasure, the right to restriction ofprocessing, the right to data portability, the right to object, theright to avoid automated decision making, and/or other rights, withregard to the subset of data of the user and/or the subset of theinformation relating thereto, as such rights are more fully describedherein. The DLDP, rights management platform, and/or governance platformcan facilitate enabling the user to exercise the set of rights withregard to the subset of data of the user and/or the subset of theinformation relating thereto, as more fully described herein.

FIG. 30 illustrates a flow diagram of an example, non-limiting method3000 that can desirably (e.g., efficiently or optimally) determine a setof obligations and corresponding set of rules relating to dataprotection, and determine compliance with the set of obligations by aset of data stores and associated entity, in accordance with variousaspects and embodiments described herein. The method 3000 can beemployed by, for example, a system comprising the DLDP, its constituentor associated platforms (e.g., governance platform), a processorcomponent (e.g., of or associated with the DLDP), and/or a data store(e.g., of or associated with the DLDP).

At 3002, items of data of users can be detected in a set of data storesassociated with an entity based at least in part on scanning of the setof data stores. At 3004, information relating to the items of data canbe generated based at least in part on the results of the scanning. Thescanner component can scan the set of data stores associated with anentity. Based at least in part on the results of scanning the set ofdata stores, the scanner component can detect the items of data of theusers that are stored in the set of data stores. The scanner component,machine learning component, or data management component can determineand generate the information relating to the items of data based atleast in part on the results of the scanning and analysis of thescanning results.

At 3006, the items of data, the information relating thereto, and a setof rules can be analyzed, wherein the set of rules can relate to a setof obligations regarding data protection, and wherein the set ofobligations can be determined to be applicable to the set of datastores. The governance component can determine the set of obligationsbased at least in part on the results of analyzing a subset of laws,regulations, and/or agreements determined to be applicable to the set ofdata stores and the entity. The governance component also can determinethe set of rules based at least in part on the set of obligations.

For instance, the governance component can employ the rules engine,which can analyze the laws and regulations relating to data protectionthat are determined to be application to the jurisdiction (e.g., legaland/or geographical jurisdiction) associated with the set of data stores(e.g., the jurisdiction in which the set of data stores resides or withregard to which the set of data stores and/or items of data of usersstored therein are subject or governed). The rules engine also cananalyze an agreement (e.g., SLA) that is determined to be applicable tothe set of data stores, the entity, and/or the users. Based at least inpart on the results of analyzing the subset of laws, regulations, and/oragreements, the rules engine can determine the set of obligations,comprising legal obligations and/or contractual obligations, that stemfrom the subset of laws, regulations, and/or agreements. The rulesengine can determine and generate the set of rules based at least inpart on the set of obligations, as more fully described herein.

At 3008, based at least in part on the results of the analysis, adetermination can be made regarding whether the set of data stores is incompliance with the set of obligations. Based at least in part on theanalysis results, the governance component can determine whether the setof data stores and associated entity are in compliance with the set ofobligations. For instance, the governance component can perform acompliance assessment on the set of data stores to determine the extentor level of compliance of the set of data stores with the set of rulesand correspondingly the set of obligations. Based at least in part onthe results of the compliance assessment, the governance component candetermine the extent or level of compliance of the set of data stores,and associated entity, with the set of rules and corresponding set ofobligations, in accordance with the defined data management criteria.The compliance assessment also can indicate an extent or level ofcompliance of the DLDP and/or its constituent or associated platformswith the set of rules and corresponding set of obligations as well.Depending in part on the results of the compliance assessment, thegovernance component or DLDP, for example can present (e.g., report ordisplay) information relating to the compliance assessment (e.g., via auser interface component) and indicating the extent or level ofcompliance of the set of data stores and associated entity (and/or theDLDP and/or its constituent or associated platforms), or can generate anotification message or exception ticket to indicate an anomaly that canindicate that there is a non-compliance or potential non-complianceissue, or another anomaly that is to be evaluated and/or resolved (e.g.,checked out and/or remediated by an appropriate representative of orassociated with the entity).

FIG. 31 illustrates a flow diagram of another example, non-limitingmethod 3100 that can desirably identify data, data types of data, andlanguages of data stored in data stores associated with entities, inaccordance with various aspects and embodiments described herein. Themethod 3100 can be employed by, for example, a system comprising theDLDP, its constituent or associated platforms (e.g., governanceplatform, rights management platform, etc.), a processor component(e.g., of or associated with the DLDP), and/or a data store (e.g., of orassociated with the DLDP).

At 3102, first data stored in a first data store associated with a firsttenant entity can be scanned, wherein the first data can be associatedwith a first user. At 3104, a first language and a first data type ofthe first data can be identified based at least in part on the scanningof the first data and a machine learning function. The scanner componentcan scan the first data store associated with the first tenant entity.Based at least in part on the results of scanning the first data store,the scanner component can detect the first data of the first user thatis stored in the first data store. The scanner component or datamanagement component, employing the machine learning component, canidentify or determine the first language and the first data type of thefirst data, based at least in part on the scanning results and themachine learning function of the machine learning component.

At 3106, second data stored in a second data store associated with asecond tenant entity can be scanned, wherein the second data can beassociated with a second user. At 3108, a second language and a seconddata type of the second data can be identified based at least in part onthe scanning of the second data and the machine learning function. Thescanner component can scan the second data store associated with thesecond tenant entity. Based at least in part on the results of scanningthe second data store, the scanner component can detect the second dataof the second user that is stored in the second data store. The scannercomponent or data management component, employing the machine learningcomponent, can identify or determine the second language and the seconddata type of the second data, based at least in part on the scanningresults and the machine learning function of the machine learningcomponent.

FIG. 32 illustrates a flow diagram of another example, non-limitingmethod 3200 that can desirably (e.g., efficiently or optimally)determine respective risk scores associated with KRI metrics, privacyprinciples, and/or data management platforms, in accordance with variousaspects and embodiments described herein. The method 3200 can beemployed by, for example, a system comprising the DLDP, its constituentor associated platforms (e.g., governance platform), a processorcomponent (e.g., of or associated with the DLDP), and/or a data store(e.g., of or associated with the DLDP).

At 3202, KRI metrics can be analyzed in relation to items of data ofusers stored in a set of data stores associated with an entity and alevel of compliance with a set of rules and corresponding set ofobligations. The governance component (e.g., employing a risk assessmentcomponent) can analyze the KRI metrics in relation to items of datastored in the set of data stores associated with the entity and thelevel of compliance with the set of rules and corresponding set ofobligations by the set of data stores, the entity, and/or the DLDP orits constituent or associated platforms. The governance component (e.g.,employing a rules engine) can determine the set of obligations (e.g.,legal and/or contractual obligations) based at least in part on theresults of analyzing information relating to a law(s) and/or anagreement(s) that is applicable to the entity and/or the set of datastores. The governance component can determine the set of rules based atleast in part on the set of obligations. Respective KRI metrics canrelate to respective privacy principles, one or more respective sourceor data management platforms (e.g., DLDP, governance platform, rightsmanagement platform, DSR platform, consent management platform, thirdparty management platform, and/or custom sources platform, etc.), and/orthe set of data stores associated with the entity.

At 3204, respective risk scores can be determined with regard to therespective KRI metrics based at least in part on the results of theanalysis at reference numeral 3202. The governance component candetermine the respective risk scores associated with respective KRImetrics based at least in part on the results of such analysis. For eachKRI metric, based at least in part on the analysis, the governancecomponent can determine the amount of impact that one or moreoccurrences of one or more anomalies relating to the one or moreobligations of the set of obligations can have, with respect to the KRImetric, associated data management platform and/or the entity; and, foreach of the one or more occurrences of the one or more anomalies, candetermine the likelihood that an occurrence of an anomaly relating to anobligation.

At 3206, for each KRI metric, a weight value can be applied to the riskscore associated with the KRI metric to generate a weighted risk scoreassociated with the KRI metric. The governance component can determinerespective weight values to apply to the KRI metrics, wherein a weightvalue for one KRI metric can be different from or same as another weightvalue of another KRI metric depending on various factors (e.g., anamount of influence or importance a particular KRI metric has relativeto another KRI metric), in accordance with the defined data managementcriteria. For each KRI metric, the governance component can determine(e.g., calculate) or generate the weighted risk score associated withthe KRI metric based at least in part on the application of the weightvalue to the risk score associated with the KRI metric.

At 3208, for each privacy principle, a risk score associated with theprivacy principle can be determined based at least in part on respectiveweighted risk scores associated with respective KRI metrics that areassociated with the privacy principle. For each privacy principle, thegovernance component can determine the risk score associated with theprivacy principle based at least in part on (e.g., as a function of)respective weighted risk scores associated with respective KRI metricsthat are associated with (e.g., related or applicable to) the privacyprinciple. For example, for each privacy principle, the governancecomponent can determine the risk score associated with the privacyprinciple as an average risk score, a median risk score, a trimmedaverage or mean risk score, or a normalized risk score derived from theapplicable weighted risk scores of KRI metrics associated with theprivacy principle, or as a peak weighted risk score of all theapplicable weighted risk scores associated with the privacy principle.The defined data management criteria can indicate which type of riskscore determination (e.g., average, median, trimmed average, trimmedmean, normalized, or peak) is to be used.

At 3210, for each privacy principle, a weight value can be applied tothe risk score associated with the privacy principle to generate aweighted risk score associated with the privacy principle. Thegovernance component can determine respective weight values to apply tothe respective privacy principles, wherein a weight value for oneprivacy principle can be different from or same as another weight valueof another privacy principle depending on various factors (e.g., anamount of influence or importance a particular privacy principle hasrelative to another privacy principle), in accordance with the defineddata management criteria. For each privacy principle, the governancecomponent can determine (e.g., calculate) or generate the weighted riskscore associated with the privacy principle based at least in part onthe application of the weight value to the risk score associated withthe privacy principle.

At 3212, for each data management platform, a risk score associated withthe data management platform can be determined based at least in part onrespective weighted risk scores associated with respective privacyprinciples that are associated with the data management platform. Foreach data management platform, the governance component can determinethe risk score associated with the data management platform based atleast in part on (e.g., as a function of) respective weighted riskscores associated with respective privacy principles that are associatedwith (e.g., related or applicable to) the data management platform. Forexample, for each data management platform, the governance component candetermine the risk score associated with the data management platform asan average, a median, a trimmed average, a trimmed mean, or a normalizedrisk score derived from the applicable weighted risk scores associatedwith the data management platform, or as a peak weighted risk score ofall the applicable weighted risk scores associated with the privacyprinciple. The defined data management criteria can indicate which typeof risk score determination (e.g., average, median, trimmed average,trimmed mean, normalized, or peak) is to be used

At 3214, for each data management platform, a weight value can beapplied to the risk score associated with the data management platformto generate a weighted risk score associated with the data managementplatform. The governance component can determine respective weightvalues to apply to the respective data management platforms, wherein aweight value for one data management platform can be different from orsame as another weight value of another data management platformdepending on various factors (e.g., an amount of influence or importancea particular data management platform has relative to another datamanagement platform). For each data management platform, the governancecomponent can determine (e.g., calculate) or generate the weighted riskscore associated with the data management platform based at least inpart on the application of the weight value to the risk score associatedwith the data management platform.

At 3216, an overall risk score by platforms and privacy principles canbe determined based at least in part on the respective weighted riskscores associated with the data management platforms. The governancecomponent can determine (e.g., calculate) the overall risk score byplatforms and privacy principles based at least in part on (e.g., as afunction of) the respective weighted risk scores associated with therespective data management platforms, wherein the respective weightedrisk scores associated with the respective data management platforms canbe derived in part from the respective weighted risk scores associatedwith the respective privacy principles, such as described herein.

At 3218, the overall risk score by platforms and privacy principles, therisk scores associated with the data management platforms, the riskscores associated with the privacy principles, and/or the risk scoresassociated with the KRI metrics can be presented via a user interface.The governance platform can facilitate presenting (e.g., displaying orconveying), via the user interface component, the overall risk score byplatforms and privacy principles and/or risk scores associated with thedata management platforms, privacy principles, and/or the KRI metrics.An authorized and/or authenticated user can view, via the user interfacecomponent, the overall risk score by platforms and privacy principlesand/or risk scores associated with the data management platforms,privacy principles, and/or the KRI metrics. Additionally oralternatively, the authorized and/or authenticated user can view, viathe user interface component, the underlying data that was utilized todetermine the respective risk scores.

At this point, the method 3200 can proceed to reference point A,wherein, in some embodiments, the method 3300 of FIG. 33 can proceedfrom reference point A, as more fully described herein.

FIG. 33 illustrates a flow diagram of another example, non-limitingmethod 3300 that can desirably (e.g., efficiently or optimally)determine a privacy health index associated with an entity that isassociated with a set of data stores that store data of users, inaccordance with various aspects and embodiments described herein. Themethod 3300 can be employed by, for example, a system comprising theDLDP, its constituent or associated platforms (e.g., governanceplatform), a processor component (e.g., of or associated with the DLDP),and/or a data store (e.g., of or associated with the DLDP). In someembodiments, the method 3300 can proceed from reference point A of themethod 3200 of FIG. 32.

At 3302, with regard to the data management platforms and the set ofdata stores, information relating to risk controls associated with thedata management platforms and the set of data stores, exceptionindicators relating to anomalies associated with the data managementplatforms and the set of data stores, and remediation measuresimplemented to remedy or mitigate anomalies associated with the datamanagement platforms and the set of data stores can be analyzed. Withregard to the data management platforms and the set of data stores, thegovernance component can analyze the information relating to the riskcontrols, the exception indicators, and the remediation measuresassociated with the data management platforms and the set of datastores.

At 3304, based at least in part on the overall risk score by platformsand privacy principles, and the results of analyzing the respectiveinformation relating to the risk controls, the exception indicators, andthe remediation measures, a privacy health index associated with theentity, the set of data stores, and/or the data management platformsoverall can be determined. In some embodiments, for each data managementplatform or data store, the governance component can quantify (e.g.,determine or calculate a value for) the results of analyzing respectiveinformation relating to the risk controls, the exception indicators, andthe remediation measures associated with the data management platform ordata store. The governance component can determine (e.g., calculate) theprivacy health index (e.g., privacy health index value, rating, orscore) associated with the entity, the set of data stores, and/or thedata management platforms overall based at least in part on (e.g., as afunction of) the overall risk score by platforms and privacy principles,and the one or more quantifying values associated with the riskcontrols, the exception indicators, and the remediation measures, asderived from the analysis of the information.

At 3306, the privacy health index associated with the entity can bepresented via a user interface. The governance platform can facilitatepresenting (e.g., displaying or conveying), via the user interfacecomponent, the privacy health index (e.g., the privacy health indexvalue) associated with the entity, the set of data stores, and/or thedata management platforms overall. An authorized and/or authenticateduser can view, via the user interface component, the privacy healthindex. In some embodiments, the privacy health index can be presented,via the user interface component, along with the overall risk score byplatforms and privacy principles, risk scores associated with the datamanagement platforms, privacy principles, or KRI metrics, information orquantifying values associated with the risk controls, the exceptionindicators, and the remediation measures, and/or other desiredunderlying or related information.

FIG. 34 presents a flow diagram of an example, non-limiting method 3400that can determine and utilize a set of rules that can correspond to theset of obligations application to a set of data stores, an associatedentity, and/or the DLDP and its constituent or associated platforms, inaccordance with various aspects and embodiments of the disclosed subjectmatter. The method 3400 can be employed by, for example, a systemcomprising the DLDP, its constituent or associated platforms (e.g.,rights management platform, governance platform, etc.), a processorcomponent (e.g., of or associated with the DLDP), and/or a data store(e.g., of or associated with the DLDP).

At 3402, a set of laws and a set of agreements associated with a set ofdata stores, an entity, and/or one or more data management platforms canbe analyzed. The one or more data management platforms can be associatedwith the set of data stores in which items of data associated with userscan be stored, wherein the set of data stores can comprise one or moredata stores. The set of data stores can be associated with the entity.The set of laws can comprise one or more laws that can relate to dataprotection, and can be applicable to the jurisdiction(s) (e.g., legal orgeographical jurisdiction) associated with the set of data stores, theentity, and/or the one or more data management platforms associated withthe entity. The set of agreements can comprise one or more agreements(e.g., contracts) that can relate to data protection, and can beapplicable to the set of data stores, the entity, and/or the one or moredata management platforms. For instance, the set of laws and/or set ofagreements can comprise various provisions that can indicate what theentity is obliged (e.g., required) to do in order to comply with the setof laws and/or set of agreements. The governance component (e.g.,employing a rules engine) can analyze the set of laws and the set ofagreements to facilitate determining a set of obligations (e.g., legalobligations, such as legal requirements or conditions, and/orcontractual obligations, such as contractual requirements or conditions)of or associated with the entity that arise out of the set of laws andthe set of agreements.

At 3404, a set of obligations of or associated with the entity, whichcan arise out of the set of laws and the set of agreements, can bedetermined based at least in part on the results of the analysis of theset of laws and the set of agreements. Based at least in part on theresults of analyzing the set of laws and/or set of agreements, thegovernance component can identify or determine the set of obligations ofor associated with the entity and/or the set of data managementplatforms.

At 3406, a set of rules, which can correspond to the set of obligations,can be determined based at least in part on the set of obligations. Thegovernance component can determine the set of rules based at least inpart on the set of obligations. For example, if a legal or contractualobligation indicates that a particular type of information (e.g., SocialSecurity Number, financial account number, etc.) of users is to besecured from being accessed by unauthorized users, the governancecomponent (e.g., employing the rules engine) can determine and generatea rule that can indicate or provide that the particular type ofinformation of users is to be secured from being accessed byunauthorized users and only can be accessed by users who satisfy certainauthorization and/or authentication conditions.

At 3408, the set of rules can be applied to the set of data stores, theentity, and/or the one or more data management platforms to facilitateenforcing the set of rules against the set of data stores, the entity,and/or the one or more data management platforms. The governanceplatform can apply and enforce the set of rules against the set of datastores, the entity, and/or the one or more data management platforms tofacilitate securing (e.g., protecting) items of data associated withusers, in accordance with the set of obligations, and accordingly, theset of laws and/or the set of agreements.

FIG. 35 depicts a flow diagram of an example, non-limiting method 3500that can determine an anomaly with regard to data of users has beendetected and initiate a remediation action to remedy or mitigate theanomaly, in accordance with various aspects and embodiments of thedisclosed subject matter. The method 3500 can be employed by, forexample, a system comprising the DLDP, its constituent or associatedplatforms (e.g., governance platform, rights management platform, etc.),a processor component (e.g., of or associated with the DLDP), and/or adata store (e.g., of or associated with the DLDP).

At 3502, a set of data stores associated with an entity and a set ofdata management platforms can be monitored. The governance component canmonitor and/or track activity (e.g., requests for data, access of data,usage of data, etc.) of or associated with the set of data stores andthe set of data management platforms. The entity that operates, owns, ormanages the set of data management platforms can be same or differententity than the one that operates, owns, or manages the set of datastores. Such monitoring and/or tracking can be performed by thegovernance component to determine whether items of data of users thatare stored in or associated with the set of data stores, and/orinformation relating to the items of data, are being secured inaccordance with a set of rules relating to data protection. Thegovernance component can determine the set of rules based at least inpart on obligations (e.g., legal and/or contractual obligations)determined from a law(s) or agreement(s) relating to data protection,and associated with the entity and/or the set of data managementplatforms, as more fully described herein.

At 3504, based at least in part on the monitoring and/or tracking, adetermination can be made regarding whether a condition has beensatisfied that indicates an anomaly relating to data protectionassociated with the set of data stores or the set of data managementplatforms is detected. Based at least in part on the monitoring and/ortracking, the governance component can determine whether a condition hasbeen satisfied (e.g., a defined threshold value of a condition has beenmet, breached, or exceeded) that indicates that an anomaly (e.g., anon-compliance issue, potential non-compliance issue, or other anomaly)has occurred and has been detected. The condition can relate to a rulerelating to data protection being breached or potentially beingbreached. For example, a breach of a condition and associated rule canrelate to an undesirable number of users (e.g., a defined thresholdnumber of users) continuing to receive solicitation emails from theentity, via a platform of or associated with the entity, beyond adefined period of time (e.g., 30 days) after the users have requested tono longer receive such solicitation emails. As some other examples, abreach of a condition and associated rule can relate to a sensitive orprivate type of information associated with a user being improperly(e.g., illegally or without authorization) collected by a datamanagement platform or improperly accessed from the platform by anotheruser.

If it is determined that the condition has not been satisfied, which canindicate that no anomaly has been detected, the method 3500 can returnto reference numeral 3502 wherein the set of data stores and the set ofdata management platforms can continue to be monitored. If, instead, atreference numeral 3504, it is determined that the condition has beensatisfied (e.g., breached), which can indicate that an anomaly has beendetected, the method 3500 can proceed to reference numeral 3506.

At 3506, in response to detecting that the condition has been satisfiedindicating the anomaly is detected, an exception indicator can begenerated, wherein the exception indicator can indicate that the anomalyhas been detected. In response to detecting that the condition has beensatisfied indicating the anomaly is detected, the governance component,employing an exception engine, can generate the exception indicator(e.g., exception ticket or message).

At 3508, the exception indicator can be communicated to facilitateremediation of the anomaly. In some embodiments, the exception enginecan communicate the exception indicator to a remediation componentand/or a person associated with the entity to facilitate remediation ofthe anomaly.

At 3510, a remediation action can be performed to remedy or mitigate theanomaly. The remediation component, of or associated with the governancecomponent, and/or the person can perform a desired remediation action(e.g., remediation measure) to remedy or mitigate the anomaly. Forexample, if the anomaly involves an undesirable number of users (e.g., adefined threshold number of users) continuing to receive solicitationemails from the entity, via a platform of or associated with the entity,beyond a defined period of time after the users have requested to nolonger receive such solicitation emails, the desired remediation actioncan comprise instructing the person of or associated with the entity toreview code relating to the sending of solicitation emails and, ifappropriate, to modify the code to ensure that undesired solicitationemails are no longer sent to users who have requested to no longerreceive such solicitation emails. For instance, a notification componentcan send a notification message, comprising information relating to theexception indicator, to the person to notify the person of the anomalyand request that a remediation action be taken or performed to remedy ormitigate the anomaly.

In some embodiments, the exception ticket or notification message canrequest that the person validate (e.g., verify) the anomaly to ensurethat an actual anomaly exists and has to be addressed (e.g.,remediated). If the person determines that the anomaly is not valid, theperson can send a message (e.g., using communication device) to thegovernance platform, wherein the message can indicate the anomaly wasdetermined to not be valid, so no remediation action was taken.

At 3512, remediation information, which can indicate that the anomalyhas been remedied or mitigated, can be received. In response to theanomaly being remedied or mitigated, the remediation component cancommunicate the remediation information, which can indicate that theanomaly has been remedied or mitigated, to the exception engine or othercomponent of the governance component to indicate that the anomaly hasbeen remedied or mitigated to bring the entity and/or associated datamanagement platform into compliance with the rule(s) and associatedobligation(s).

At 3514, information relating to a KRI metric(s) associated with the setof data stores and/or a data management platform(s), a risk score(s)associated with the KRI metric(s), platform(s), or set of data stores,and/or a privacy health index associated with the entity can be updatedin response to the anomaly being remedied or mitigated. In response tothe remediation information indicating that the anomaly has beenremedied or mitigated, the governance component can update theinformation relating to the KRI metric(s), the risk score(s) associatedwith the KRI metric(s), platform(s), or set of data stores, and/or theprivacy health index associated with the entity to indicate or reflectthat (e.g., to take into account that) the anomaly has been remedied ormitigated. For example, the governance component can update a risk scoreassociated with the KRI metric or associated platform to decrease therisk score and/or can update the privacy health index to increase theprivacy health index based at least in part on the remediationinformation indicating that the anomaly has been remedied or mitigated.

In order to provide additional context for various embodiments describedherein, FIG. 36 and the following discussion are intended to provide abrief, general description of a suitable computing environment 3600 inwhich the various embodiments of the embodiment described herein can beimplemented. While the embodiments have been described above in thegeneral context of computer-executable instructions that can run on oneor more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, Internet of Things (IoT)devices, distributed computing systems, as well as personal computers,hand-held computing devices, microprocessor-based or programmableconsumer electronics, and the like, each of which can be operativelycoupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 36, the example environment 3600 forimplementing various embodiments of the aspects described hereinincludes a computer 3602, the computer 3602 including a processing unit3604, a system memory 3606 and a system bus 3608. The system bus 3608couples system components including, but not limited to, the systemmemory 3606 to the processing unit 3604. The processing unit 3604 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 3604.

The system bus 3608 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 3606includes ROM 3610 and RAM 3612. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer3602, such as during startup. The RAM 3612 can also include a high-speedRAM such as static RAM for caching data.

The computer 3602 further includes an internal hard disk drive (HDD)3614 (e.g., EIDE, SATA), one or more external storage devices 3616(e.g., a magnetic floppy disk drive (FDD) 3616, a memory stick or flashdrive reader, a memory card reader, etc.) and a drive 3620, e.g., suchas a solid state drive, an optical disk drive, which can read or writefrom a disk 3622, such as a CD-ROM disc, a DVD, a BD, etc.Alternatively, where a solid state drive is involved, disk 3622 wouldnot be included, unless separate. While the internal HDD 3614 isillustrated as located within the computer 3602, the internal HDD 3614can also be configured for external use in a suitable chassis (notshown). Additionally, while not shown in environment 3600, a solid statedrive (SSD) could be used in addition to, or in place of, an HDD 3614.The HDD 3614, external storage device(s) 3616 and drive 3620 can beconnected to the system bus 3608 by an HDD interface 3624, an externalstorage interface 3626 and a drive interface 3628, respectively. Theinterface 3624 for external drive implementations can include at leastone or both of Universal Serial Bus (USB) and Institute of Electricaland Electronics Engineers (IEEE) 1394 interface technologies. Otherexternal drive connection technologies are within contemplation of theembodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 3602, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 3612,including an operating system 3630, one or more application programs3632, other program modules 3634 and program data 3636. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 3612. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 3602 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 3630, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 36. In such an embodiment, operating system 3630 can comprise onevirtual machine (VM) of multiple VMs hosted at computer 3602.Furthermore, operating system 3630 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 3632. Runtime environments are consistent executionenvironments that allow applications 3632 to run on any operating systemthat includes the runtime environment. Similarly, operating system 3630can support containers, and applications 3632 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 3602 can be enable with a security module, such as atrusted processing module (TPM). For instance with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 3602, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 3602 throughone or more wired/wireless input devices, e.g., a keyboard 3638, a touchscreen 3640, and a pointing device, such as a mouse 3642. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 3604 through an input deviceinterface 3644 that can be coupled to the system bus 3608, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 3646 or other type of display device can be also connected tothe system bus 3608 via an interface, such as a video adapter 3648. Inaddition to the monitor 3646, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 3602 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 3650. The remotecomputer(s) 3650 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer3602, although, for purposes of brevity, only a memory/storage device3652 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 3654 and/orlarger networks, e.g., a wide area network (WAN) 3656. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 3602 can beconnected to the local network 3654 through a wired and/or wirelesscommunication network interface or adapter 3658. The adapter 3658 canfacilitate wired or wireless communication to the LAN 3654, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 3658 in a wireless mode.

When used in a WAN networking environment, the computer 3602 can includea modem 3660 or can be connected to a communications server on the WAN3656 via other means for establishing communications over the WAN 3656,such as by way of the Internet. The modem 3660, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 3608 via the input device interface 3644. In a networkedenvironment, program modules depicted relative to the computer 3602 orportions thereof, can be stored in the remote memory/storage device3652. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer3602 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 3616 asdescribed above, such as but not limited to a network virtual machineproviding one or more aspects of storage or processing of information.Generally, a connection between the computer 3602 and a cloud storagesystem can be established over a LAN 3654 or WAN 3656 e.g., by theadapter 3658 or modem 3660, respectively. Upon connecting the computer3602 to an associated cloud storage system, the external storageinterface 3626 can, with the aid of the adapter 3658 and/or modem 3660,manage storage provided by the cloud storage system as it would othertypes of external storage. For instance, the external storage interface3626 can be configured to provide access to cloud storage sources as ifthose sources were physically connected to the computer 3602.

The computer 3602 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

FIG. 37 is a schematic block diagram of a sample computing environment3700 with which the disclosed subject matter can interact. The samplecomputing environment 3700 includes one or more client(s) 3710. Theclient(s) 3710 can be hardware and/or software (e.g., threads,processes, computing devices). The sample computing environment 3700also includes one or more server(s) 3730. The server(s) 3730 can also behardware and/or software (e.g., threads, processes, computing devices).The servers 3730 can house threads to perform transformations byemploying one or more embodiments as described herein, for example. Onepossible communication between a client 3710 and a server 3730 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The sample computing environment 3700 includes acommunication framework 3750 that can be employed to facilitatecommunications between the client(s) 3710 and the server(s) 3730. Theclient(s) 3710 are operably connected to one or more client datastore(s) 3720 that can be employed to store information local to theclient(s) 3710. Similarly, the server(s) 3730 are operably connected toone or more server data store(s) 3740 that can be employed to storeinformation local to the servers 3730.

The disclosed subject matter can be a system, a method, an apparatusand/or a computer program product at any possible technical detail levelof integration. The computer program product can include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thedisclosed subject matter. The computer readable storage medium can be atangible device that can retain and store instructions for use by aninstruction execution device. The computer readable storage medium canbe, for example, but is not limited to, an electronic storage device, amagnetic storage device, an optical storage device, an electromagneticstorage device, a semiconductor storage device, or any suitablecombination of the foregoing. A non-exhaustive list of more specificexamples of the computer readable storage medium can also include thefollowing: a portable computer diskette, a hard disk, a random accessmemory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM or Flash memory), a static random access memory(SRAM), a portable compact disc read-only memory (CD-ROM), a digitalversatile disk (DVD), a memory stick, a floppy disk, a mechanicallyencoded device such as punch-cards or raised structures in a groovehaving instructions recorded thereon, and any suitable combination ofthe foregoing. A computer readable storage medium, as used herein, isnot to be construed as being transitory signals per se, such as radiowaves or other freely propagating electromagnetic waves, electromagneticwaves propagating through a waveguide or other transmission media (e.g.,light pulses passing through a fiber-optic cable), or electrical signalstransmitted through a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network can comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device. Computer readable programinstructions for carrying out operations of the disclosed subject mattercan be assembler instructions, instruction-set-architecture (ISA)instructions, machine instructions, machine dependent instructions,microcode, firmware instructions, state-setting data, configuration datafor integrated circuitry, or either source code or object code writtenin any combination of one or more programming languages, including anobject oriented programming language such as Smalltalk, C++, or thelike, and procedural programming languages, such as the “C” programminglanguage or similar programming languages. The computer readable programinstructions can execute entirely on the user's computer, partly on theuser's computer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer can beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection can be made to an external computer (for example, through theInternet using an Internet Service Provider). In some embodiments,electronic circuitry including, for example, programmable logiccircuitry, field-programmable gate arrays (FPGA), or programmable logicarrays (PLA) can execute the computer readable program instructions byutilizing state information of the computer readable programinstructions to personalize the electronic circuitry, in order toperform aspects of the disclosed subject matter.

Aspects of the disclosed subject matter are described herein withreference to flowchart illustrations and/or block diagrams of methods,apparatus (systems), and computer program products according toembodiments of the disclosed subject matter. It will be understood thateach block of the flowchart illustrations and/or block diagrams, andcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer readable program instructions.These computer readable program instructions can be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionscan also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks. The computer readable program instructions can also be loadedonto a computer, other programmable data processing apparatus, or otherdevice to cause a series of operational acts to be performed on thecomputer, other programmable apparatus or other device to produce acomputer implemented process, such that the instructions which executeon the computer, other programmable apparatus, or other device implementthe functions/acts specified in the flowchart and/or block diagram blockor blocks.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the disclosed subject matter. In this regard, each blockin the flowchart or block diagrams can represent a module, segment, orportion of instructions, which comprises one or more executableinstructions for implementing the specified logical function(s). In somealternative implementations, the functions noted in the blocks can occurout of the order noted in the Figures. For example, two blocks shown insuccession can, in fact, be executed substantially concurrently, or theblocks can sometimes be executed in the reverse order, depending uponthe functionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

While the subject matter has been described above in the general contextof computer-executable instructions of a computer program product thatruns on a computer and/or computers, those skilled in the art willrecognize that this disclosure also can or can be implemented incombination with other program modules. Generally, program modulesinclude routines, programs, components, data structures, etc. thatperform particular tasks and/or implement particular abstract datatypes. Moreover, those skilled in the art will appreciate that theinventive computer-implemented methods can be practiced with othercomputer system configurations, including single-processor ormultiprocessor computer systems, mini-computing devices, mainframecomputers, as well as computers, hand-held computing devices (e.g., PDA,phone), microprocessor-based or programmable consumer or industrialelectronics, and the like. The illustrated aspects can also be practicedin distributed computing environments in which tasks are performed byremote processing devices that are linked through a communicationsnetwork. However, some, if not all aspects of this disclosure can bepracticed on stand-alone computers. In a distributed computingenvironment, program modules can be located in both local and remotememory storage devices.

As used in this application, the terms “component,” “system,”“platform,” “interface,” and the like, can refer to and/or can include acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component can be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution and a component canbe localized on one computer and/or distributed between two or morecomputers. In another example, respective components can execute fromvarious computer readable media having various data structures storedthereon. The components can communicate via local and/or remoteprocesses such as in accordance with a signal having one or more datapackets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across a networksuch as the Internet with other systems via the signal). As anotherexample, a component can be an apparatus with specific functionalityprovided by mechanical parts operated by electric or electroniccircuitry, which is operated by a software or firmware applicationexecuted by a processor. In such a case, the processor can be internalor external to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts, wherein the electroniccomponents can include a processor or other means to execute software orfirmware that confers at least in part the functionality of theelectronic components. In an aspect, a component can emulate anelectronic component via a virtual machine, e.g., within a cloudcomputing system.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form. As used herein, the terms “example”and/or “exemplary” are utilized to mean serving as an example, instance,or illustration. For the avoidance of doubt, the subject matterdisclosed herein is not limited by such examples. In addition, anyaspect or design described herein as an “example” and/or “exemplary” isnot necessarily to be construed as preferred or advantageous over otheraspects or designs, nor is it meant to preclude equivalent exemplarystructures and techniques known to those of ordinary skill in the art.

As it is employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Further, processors can exploit nano-scalearchitectures such as, but not limited to, molecular and quantum-dotbased transistors, switches and gates, in order to optimize space usageor enhance performance of user equipment. A processor can also beimplemented as a combination of computing processing units. In thisdisclosure, terms such as “store,” “storage,” “data store,” datastorage,” “database,” and substantially any other information storagecomponent relevant to operation and functionality of a component areutilized to refer to “memory components,” entities embodied in a“memory,” or components comprising a memory. It is to be appreciatedthat memory and/or memory components described herein can be eithervolatile memory or nonvolatile memory, or can include both volatile andnonvolatile memory. By way of illustration, and not limitation,nonvolatile memory can include read only memory (ROM), programmable ROM(PROM), electrically programmable ROM (EPROM), electrically erasable ROM(EEPROM), flash memory, or nonvolatile random access memory (RAM) (e.g.,ferroelectric RAM (FeRAM)). Volatile memory can include RAM, which canact as external cache memory, for example. By way of illustration andnot limitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM),direct Rambus RAM (DRRAM), direct Rambus dynamic RAM (DRDRAM), andRambus dynamic RAM (RDRAM). Additionally, the disclosed memorycomponents of systems or computer-implemented methods herein areintended to include, without being limited to including, these and anyother suitable types of memory.

It is to be appreciated and understood that components (e.g.,communication device, communication network, pool management component,pool component, event component, contact management component,artificial intelligence component, processor component, data store,etc.), as described with regard to a particular system or method, caninclude the same or similar functionality as respective components(e.g., respectively named components or similarly named components) asdescribed with regard to other systems or methods disclosed herein.

What has been described above include mere examples of systems andcomputer-implemented methods. It is, of course, not possible to describeevery conceivable combination of components or computer-implementedmethods for purposes of describing this disclosure, but one of ordinaryskill in the art can recognize that many further combinations andpermutations of this disclosure are possible. Furthermore, to the extentthat the terms “includes,” “has,” “possesses,” and the like are used inthe detailed description, claims, appendices and drawings such terms areintended to be inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments disclosed. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the described embodiments. The terminologyused herein was chosen to best explain the principles of theembodiments, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A system, comprising: a processor that executescomputer-executable components stored in a memory, thecomputer-executable components comprising: a secure data store thatstores information relating to items of data of users stored in a set ofdata stores associated with the system, wherein the information isgenerated based on scanning of the set of data stores; and a datamanagement component that controls detection of presence of the items ofdata in the set of data stores to enable a determination relating tocompliance of the set of data stores with a set of obligations relatingto data protection with regard to the items of data, wherein thedetermination is based on an analysis of the information relating to theitems of data.
 2. The system of claim 1, wherein the data managementcomponent receives the information relating to the items of data from ascanner component that scans the items of data stored in the set of datastores associated with one or more entities.
 3. The system of claim 2,wherein the scanner component generates the information relating to theitems of data based on the scanning of the items of data stored in theset of data stores and communicates at least the information to the datamanagement component, and wherein the items of data comprise astructured item of data, an unstructured item of data, or an item ofimage data.
 4. The system of claim 2, wherein the computer-executablecomponents further comprise: a classifier component that is associatedwith the scanner component, wherein the classifier component analyzes atleast an item of data of the items of data scanned by the scannercomponent, and based on the analysis of the item of data, identifiescharacters in the item of data, a language associated with thecharacters, or a data type of the item of data.
 5. The system of claim4, wherein the computer-executable components further comprise: amachine learning component that employs machine learning to learn toidentify types of characters in data, types of languages associated withthe characters, or data types of the data, based on a machine learninganalysis of historical information relating to the types of characters,the types of languages, or the data types, and wherein, based on thelearning and results of the machine learning analysis of the historicalinformation, the capability of the classifier component to identify thecharacters in the item of data, the language associated with thecharacters, or the data type of the item of data is enhanced.
 6. Thesystem of claim 5, wherein the machine learning component samples asubset of the items of data stored in the set of data stores, performs amachine learning analysis on the subset of the items of data, and, basedon a result of the machine learning analysis of the subset of the itemsof data, determines a modification relating to an online presentation ofa product or service offer that enhances the product or service offerpresented to potential customers via an electronic communication, andwherein the data management component facilitates implementing themodification.
 7. The system of claim 1, wherein the set of data storesis a first set of data stores associated with a first jurisdiction and afirst entity, wherein the set of obligations is a first set ofobligations that is determined based on a first law relating to the dataprotection or a first agreement relating to the data protection, whereinthe set of rules is a first set of rules that is determined based on thefirst set of obligations, wherein the information is first information,wherein the first law is associated with the first jurisdiction, andwherein the data management component determines a first level ofcompliance of the first set of data stores with the first set ofobligations, based on an analysis of the first information and the firstset of rules that correspond to the first set of obligations.
 8. Thesystem of claim 7, wherein the data management component analyzes secondinformation relating to second items of data stored in a second set ofdata stores associated with a second jurisdiction and a second entity,wherein the data management component determines a second level ofcompliance of the second set of data stores with a second set ofobligations associated with the second set of data stores, based on ananalysis of the second information and a second set of rules thatcorrespond to the second set of obligations, wherein the second set ofobligations is determined based on a second law relating to the dataprotection or a second agreement relating to the data protection, andwherein the second law is associated with the second jurisdiction. 9.The system of claim 1, wherein the data management component controlsaccess to the information stored in the secure data store or the itemsof data stored in the set of data stores, based on the set of rules. 10.The system of claim 9, wherein the items of data comprise a first itemof data, a second item of data, and a third item of data, wherein, inaccordance with the set of rules, the data management componentclassifies the first item of data as protected data and restricts accessto the protected data to only permit a first group of authorized usersaccess to the protected data, classifies the second item of data assensitive data and restricts access to the sensitive data to only permita second group of authorized users access to the sensitive data, andclassifies the third item of data as non-sensitive data and permits athird group of authorized users access to the non-sensitive data. 11.The system of claim 10, wherein the computer-executable componentsfurther comprise: a user interface component that presents a locked iconthat indicates that access to the protected data is restricted to thefirst group of authorized users, a sensitive icon that indicates thataccess to the sensitive data is restricted to the second group ofauthorized users, and a non-sensitive icon that indicates that access tothe non-sensitive data is permitted by the third group of authorizedusers.
 12. The system of claim 1, wherein the level of compliance is afirst level of compliance, and wherein the system further comprises adata lifecycle discovery platform that comprises the secure data storeand the data management component, and wherein the data managementcomponent determines a second level of compliance of the data lifecyclediscovery platform with at least the set of obligations based on atleast the set of rules.
 13. The system of claim 12, wherein the datamanagement component determines risk scores associated with key riskindicator metrics and privacy principles based on a risk assessmentanalysis of the key risk indicator metrics in relation to the firstlevel of compliance, the second level of compliance, an amount of impactthat an occurrence of a non-compliance issue relating to an obligationof the set of obligations is determined to have on an entity associatedwith the set of data stores or on the data lifecycle discovery platform,or a likelihood of the non-compliance issue occurring.
 14. The system ofclaim 13, wherein the computer-executable components further comprise: auser interface component that presents first compliance informationrelating to the first level of compliance, second compliance informationrelating to the second level of compliance, or at least a portion of therisk scores, wherein the risk scores comprise a first risk scoreassociated with the entity and the set of data stores, and a second riskscore associated with the data lifecycle discovery platform.
 15. Acomputer-implemented method, comprising: storing, by a system having aprocessor and a memory, information in a secure data store of a datalifecycle discovery platform, wherein the information relates to itemsof data that are stored in a set of database components associated withone or more entities, and wherein the information is generated inresponse to scanning of the items of data in the set of databasecomponents; and managing, by the system, discovery of presence of theitems of data in the set of database components to facilitate adetermination relating to adherence of the set of database componentswith a set of provisions relating to data privacy and security withregard to the items of data, wherein the determination is based on ananalysis of the information relating to the items of data.
 16. Thecomputer-implemented method of claim 15, further comprising: scanning,by the system, the items of data stored in the set of databasecomponents associated with one or more entities, wherein the items ofdata comprise a structured item of data, an unstructured item of data,or an item of image data; and generating, by the system, the informationrelating to the items of data based on the scanning of the items ofdata.
 17. The computer-implemented method of claim 15, furthercomprising: determining, by the system, a set of rules based on the setof provisions, wherein the set of database components is associated witha jurisdiction and an entity, wherein the set of provisions isdetermined based on a law relating to the data privacy and security, oran agreement relating to the data privacy and security, wherein the lawis associated with the jurisdiction.
 18. The computer-implemented methodof claim 17, further comprising: determining, by the system, a firstdegree of adherence of the set of database components with the set ofprovisions based on the determination and the set of rules; determining,by the system, a second degree of adherence of the data lifecyclediscovery platform with the set of provisions based on the set of rules,the information relating to the items of data, and other informationrelating to activity of the data lifecycle discovery platform withrespect to managing the items of data and the information relating tothe items of data; and determining, by the system, risk ratingsassociated with risk indicator metrics and privacy principles based on arisk assessment analysis of the risk indicator metrics in relation tothe first degree of adherence, the second degree of adherence, an amountof impact that an occurrence of a non-adherence issue relating to aprovision of the set of provisions is determined to have on an entityassociated with the set of database components or on the data lifecyclediscovery platform, or a likelihood of the non-adherence issueoccurring.
 19. The computer-implemented method of claim 15, furthercomprising: tracking, by the system, sharing of a subset of theinformation or a subset of the items of data with a third-party deviceassociated with a third-party entity; and determining, by the system, anextent to which the sharing of the subset of the information or thesubset of the items of data with the third-party device adheres to theset of provisions based on the set of rules.
 20. A machine-readablestorage medium, comprising executable instructions that, when executedby a processor, facilitate performance of operations, comprising:storing information in a secure data store of a data lifecycle discoveryplatform, wherein the information relates to items of data that arestored in a set of data storage components associated with one or moreentities, and wherein the information is generated based on scanning ofthe items of data stored in the set of data storage components;controlling detection of the items of data in the set of data storagecomponents to facilitate a determination relating to compliance of theset of data storage components with a set of duties relating to dataprivacy with regard to the items of data; determining an extent of thecompliance of the set of data storage components with the set of dutiesassociated with the set of database components, based on a result ofanalyzing the information and a set of rules that correspond to the setof duties and relate to the data privacy; and determining a portion ofthe information or a portion of the items of data that are authorized tobe presented via a user interface, based on the set of rules.